Fix importing polyfill plugins in the Rollup bundle #13017
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.
The polyfill plugins are ESM files compiled down to CJS, and thus they have an
__esModule: true
property.When bundling CJS files that have the
__esModule: true
option, Rollup matches the default Babel interop and transformsimport foo from "foo"
toconst foo = require("foo").default
(rather thanconst foo = require("foo")
, as Node.js does).This PR introduces a small Babel plugins that rewrites those specific
import foo
toimport * as foo
when bundling.I opened rollup/plugins#838 to see if the Rollup community is interested in aligning with Node.js.