feat(register): respect -C/--conditions flags in ESM #943
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
|
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
If it's preferable I can implement that logic instead of adding the dependency. |
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.
This fixes #890, and my usage. I think every package using subpath imports in
package.jsoninsteadpathsrewriting in.swcrcwill need to use conditions, and therefore will need this change to support switching to ESM.The
get-conditionspackage parsesprocess.argvandprocess.env.NODE_OPTIONS, and also adds"node", and, if--no-addonshasn't been set,"node-options".