Add scriptIncludeFilter option #40
Open
Conversation
This file contains 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
…ted as script tags
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added a new option
scriptIncludeFilterto optionally control which .js chunks are injected as script tags.By default nothing is filtered/changed
For instance:
scriptIncludeFilter: (id, fileInfo) => fileInfo.isEntryResolves Split bundles from dynamic imports are being injected. #34 and restores the original v1.6.1 behavior
(maybe this should become the default?)
scriptIncludeFilter: (id, fileInfo) => fileInfo.isEntry && id.match(/^index.*\.js$/i)Multiple entry chunks, but only
index*.jsshould be injected. My use case is web workers with rollup-plugin-off-main-thread.