Fix ESM babel configs #137
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
NullVoxPopuli
force-pushed
the
babel-esm-support
branch
from
2675dd4 to
32b8a90
Compare
Member
|
typescript-eslint did a breaking release in a patch/minor, it seems: typescript-eslint/typescript-eslint#11319 (comment) |
When using the eslint babel parser, we can't load any ESM babel config without this change. This support in @babel/eslint-parser is "experimental" in the sense that it can't be made default until babel 8, but it works fine on our supported node range on babel 7.
NullVoxPopuli
force-pushed
the
babel-esm-support
branch
from
32b8a90 to
55131d6
Compare
NullVoxPopuli
approved these changes
Nov 12, 2025
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.
When using the eslint babel parser, we can't load any ESM babel config without this change.
This support in @babel/eslint-parser is "experimental" in the sense that it can't be made default until babel 8, but it works fine on our supported node range on babel 7.