Fix #1668: Node does not use the 'development' condition with default require() - this PR removes the development condition under require for @glimmer/syntax and dependents.
#1669
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
NullVoxPopuli
changed the title
development condition under require
NullVoxPopuli
changed the title
development condition under requiredevelopment condition under require for @glimmer/syntax and dependents.
wagenet
approved these changes
Nov 27, 2024
Merged
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.
Tested locally with
require('@glimmer/syntax')until doing so did not error withERR_REQUIRE_ESM(node 22)With the existing published version, the following are broken:
This is because node does not use the
developmentcondition when it resolves requires.