[Examples] Fix build time getting progressively slower #5873
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.
Fixes #5872
Before we had watchers in
examples/rollup.config.js
that would simply copy build outputs over into/dist/
:This worked nice with running
npm run develop
and if you spawn another shell withtarget=debug_es5 npm run watch
it keeps working for a while aswell, but over time it does more and more, the two rollup processes get in some kind of "create / watch - do stuff / create do stuff again" loop or something.This can be fixed when we stop putting watchers on build outputs and instead use the rollup target configuration functions (e.g.
function buildTarget(buildType, moduleFormat)
) directly inexamples/rollup.config.js
for building the mentioned build outputs.This is not complicated by itself, but what makes the PR a bit bigger is the separation of a few functions that we need to call from the Examples rollup script.
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.