Use consistent resolve extensions alias for compiler#58725
Merged
Conversation
Member
Author
|
Current dependencies on/for this PR: This stack of pull requests is managed by Graphite. |
Member
Tests Passed |
Member
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
Next Runtimes
|
sokra
approved these changes
Nov 22, 2023
feedthejim
approved these changes
Nov 22, 2023
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.

What?
Changes the default resolve extensions to be consistent between server/client compilation.
Currently browser prefers
.mjsthen.jsand the server compiler prefers.jsthen.mjs.I added that behavior back in 2018 before mjs/cjs extensions were fully baked and many npm libraries had incorrect usage of it (PR: #5898).
In the new setup with ESM resolving in Node.js writing out the full extension is required for
.mjsfiles, meaning this "magic resolving" of a file to.mjsis no longer correct. In the future we'll likely want to remove.mjsfrom the default list of resolve extensions to align with the Node.js ESM resolver a bit more.For now we have to keep it in order to not break existing applications that rely on that behavior, an example of that seems to be contentlayer.
How?
Removed the condition and aligned it on a single list instead of separate lists.