Rewrite esm-shim plugin #444
Merged
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
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.
What
Drop the
@rollup/plugin-esm-shimplugin and rewrite one with AST parsing, due to it causes issues by the regex matching and replacing with shims. It cannot optionally inject the shims based on the usage.Improvement
The new plugin is using the AST parsing, and based on the cjs API you're using we inject the certain ones of polyfill and replace the usage. If you only use one, we won't insert two polyfills.
It can handle all the import paths,
@rollup/plugin-esm-shimwill break with@scopemodule path, but AST parsing won't have that problemResolves #442