#45156 closed defect (bug) (fixed)
SCRIPT_DEBUG with 5.0 Beta 1 for Blocks Assets
Reported by: | bordoni | Owned by: | atimmer |
---|---|---|---|
Milestone: | 5.0 | Priority: | normal |
Severity: | normal | Version: | 5.0 |
Component: | Build/Test Tools | Keywords: | has-patch commit fixed-5.0 |
Focuses: | javascript | Cc: | |
PR Number: |
Description
When I have SCRIPT_DEBUG
as true
to allow better debugging for the Blocks Editor compatibility for plugin development I get 404 to all of the assets related to the Blocks editor, I am almost sure it's due to the ZIP only shipping with the minified Version of the JS assets.
Attachments (2)
Change History (20)
This ticket was mentioned in Slack in #core-js by pento. View the logs.
12 months ago
#3
@
12 months ago
45156.diff adds webpack:dev
to grunt build
. When I put webpack:dev
before webpack:prod
I was treated with this error:
Warning: Circular reference detected (.dev[1].plugins[3].compiler.inputFileSystem._statStorage.interval._idlePrev._idleNext) Use --force to continue.
So I've put dev
behind prod
.
PS. I expect the error to be harmless, but caused by the fact that grunt is all one process and webpack doesn't play nice with this. If we ever want to change the order we can shell out to webpack using grunt-shell to make sure webpack is in it's own process.
#4
@
12 months ago
- Owner set to atimmer
- Resolution set to fixed
- Status changed from new to closed
In 43817:
#5
@
12 months ago
- Resolution fixed deleted
- Status changed from closed to reopened
As reported by @pento here https://wordpress.slack.com/archives/C5UNMSU4R/p1540375682000100
The commit above didn't seem to fix the problem.
#6
@
12 months ago
As this isn't building as expected, I've asked Systems to help investigate.
@atimmer: As a workaround, in case we can't get the build working correctly in time for beta 1, could you prepare a patch that causes the dist
and vendor
JS to always load the .min.js
versions? That'll at least stop the 404s until we can investigate further.
#7
@
12 months ago
- Milestone changed from Awaiting Review to 5.0
- Resolution set to fixed
- Status changed from reopened to closed
There was a bit of a delayed effect in the build server recognising @atimmer's fix. 🙂
I've updated the nightly build, it now includes the unminified files.
http://wordpress.org/nightly-builds/wordpress-5.0-latest.zip
#8
@
12 months ago
- Keywords fixed-5.0 added
- Resolution fixed deleted
- Status changed from closed to reopened
Reopening for trunk.
#9
@
12 months ago
- Keywords needs-patch added; fixed-5.0 removed
Can we make sure that there is no delay?
The packages were updated in [43861] which only updated the minified files in build-43690. The next unrelated commit [43862] also updated the dev files, see build-43691.
#10
@
12 months ago
@ocean90 force-build-target.diff fixes this. @omarreiss or @pento can you sign off on that patch?
Maybe that is a better component.