馃彈 Lazily build JS during default gulp
task
#24199
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#24152 added a way to lazily build extensions during the default
gulp
task. This PR goes a step further, and lazily builds all JS (except for the core runtimeamp.js
, which is eagerly built).Usage:
Highlights:
compileJs
calls inbuild-system/tasks/helpers.js
bundles.config.js
doBuildJs()
build-system/lazy-build.js
to build JS and extensionsperformBuild()
inbuild-system/tasks/build.js
dist()
inbuild-system/tasks/dist.js
Coming up:
serve.js
andserver.js
to eliminate the separate binary problem mentioned in 馃彈 Lazily build extensions during the defaultgulp
task聽#24152 (comment)gulp
task to build extensions after launching server聽#24138 (review), where the server waits when a build is in progressPartially addresses #24152 (review)
Partial fix for #24141
Follow up to #24138 and #24152