frontend build: setup for code splitting #2151
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add config to enable code splitting (not yet active due to no import() calls). Also clean the output directory of old files. Always build sourcemaps and use svelte-preprocess since svelte itself seems to generate broken sourcemaps for Typescript otherwise.
yagebu
force-pushed
the
code-splitting
branch
from
150b114 to
156f6a8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add config to enable code splitting (not yet active due to no import()
calls). Also clean the output directory of old files.
Always build sourcemaps and use svelte-preprocess since svelte itself
seems to generate broken sourcemaps for Typescript otherwise.