Add support for turbopack in Next 16 #956
Draft
+451
−116
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
|
commit: |
vicb
reviewed
Oct 21, 2025
| switch(chunkPath) { | ||
| ${Array.from(chunks).map(chunk => ` case "${ | ||
| // we only want the path after /path/to/.next/ | ||
| chunk.replace(/.*\.next\//, "") |
There was a problem hiding this comment.
Suggested change
| chunk.replace(/.*\.next\//, "") | |
| chunk.replace(/.*\\/.next\//, "") |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Introduce support for turbopack for Next 16+.
Bump e2e/experimental to 16.
It's a draft for now, need to investigate this opennextjs/opennextjs-aws#1022 (might not be necessary in every case)