fix: always load .mjs files via import
#15447
Merged
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
✅ Deploy Preview for jestjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
SimenB
force-pushed
the
always-load-mjs-via-import
branch
from
2d6ac86 to
f639a67
Compare
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.
Summary
Since Node has gotten
require(esm), we shouldn't rely onERR_REQUIRE_ESMbeing thrown.Also,
requireonly works with no TLA, so we should also handleERR_REQUIRE_ASYNC_MODULEFixes #15363 (and CI which has been broken since
require(esm)was unflagged in https://nodejs.org/en/blog/release/v22.12.0)Test plan
Added TLA to our test with
.mjsconfig file, which fails without these code changes