docs: add next.config.ts Node.js native resolver
#83561
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
ijjk
added
created-by: Next.js team
|
All broken links are now fixed, thank you! |
devjiwonchoi
force-pushed
the
jiwon/09-08-docs_add_next.config.ts_node.js_native_resolver
branch
from
8348f4d to
6952b51
Compare
There was a problem hiding this comment.
Pull Request Overview
Adds documentation for Node.js native TypeScript resolver support in next.config.ts files, enabling ECMAScript Modules (ESM) syntax when using Node.js v22.10.0 and higher.
- Documents the Node.js native TypeScript resolver feature for
next.config.ts - Explains version requirements and configuration steps for enabling the feature
- Recommends using
next.config.mtsfor CommonJS projects to avoid reparsing issues
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
icyJoseph
reviewed
Sep 16, 2025
icyJoseph
reviewed
Sep 16, 2025
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
devjiwonchoi
commented
Sep 16, 2025
abdonrd
reviewed
Sep 17, 2025
| NODE_OPTIONS=--experimental-transform-types next <command> | ||
| ``` | ||
|
|
||
| By default, Node treats `.ts` files as CommonJS. If `next.config.ts` uses ESM syntax, Node re-parses it as ESM, which works but prints a warning about performance overhead. To avoid this extra pass, use `next.config.mts` to declare ESM up front. |
There was a problem hiding this comment.
It's worth mentioning that we can keep next.config.ts if we set "type": "module"?
There was a problem hiding this comment.
Ty - we are iterating this - I think we can add a mention on how to set module, and link to Node's documentation, https://nodejs.org/api/packages.html#type
Co-authored-by: Joseph <[email protected]>
Co-authored-by: Joseph <[email protected]>
Co-authored-by: Abdón Rodríguez <[email protected]>
devjiwonchoi
force-pushed
the
jiwon/09-08-docs_add_next.config.ts_node.js_native_resolver
branch
from
457c22c to
0286ac5
Compare
icyJoseph
reviewed
Sep 17, 2025
Co-authored-by: Joseph <[email protected]>
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
devjiwonchoi
commented
Sep 17, 2025
icyJoseph
approved these changes
Sep 17, 2025
devjiwonchoi
deleted the
jiwon/09-08-docs_add_next.config.ts_node.js_native_resolver
branch
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.
This PR adds docs for using Node.js native TS resolver for
next.config.ts. It states:next.config.mtsI didn't mention how much it's faster compared to the legacy resolver (~68% faster in the hello world app - link) because the experience may vary for users.