feat(ses)!: Third-party module exports #668
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
kriskowal
commented
Apr 15, 2021
kriskowal
force-pushed
the
655-ses
branch
2 times, most recently
from
37b20a8 to
e03a577
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
BREAKING CHANGE Third-party static module interface implementations must now explicitly list their exported names. For CommonJS, this implies using a heuristic static analysis of
exportschanges. Consequently, third-party modules can now participate in linkage with ESM including support forexport * from './spec.cjs'and also named imports likeimport * from './spec.cjs'.Part 1 of #666