-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure the path of the Node.js entry chunk #5398
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
9 Ignored Deployments
|
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
✅ This change can build |
|
ed15812
to
81d7fbf
Compare
f2553bc
to
0aa5eef
Compare
81d7fbf
to
c433a30
Compare
0aa5eef
to
5dd12cf
Compare
4f392bd
to
9487de0
Compare
5dd12cf
to
e33a45f
Compare
9487de0
to
6419597
Compare
e33a45f
to
1dc1c82
Compare
Linux Benchmark for 73481b7Click to view benchmark
|
MacOS Benchmark for 73481b7
Click to view full benchmark
|
1dc1c82
to
c410319
Compare
Linux Benchmark for f596f88Click to view benchmark
|
c410319
to
5050577
Compare
Linux Benchmark for a3a98f7Click to view benchmark
|
MacOS Benchmark for a3a98f7
Click to view full benchmark
|
5050577
to
6a09e10
Compare
Linux Benchmark for 27dc99aClick to view benchmark
|
MacOS Benchmark for 27dc99a
Click to view full benchmark
|
Test Case fails with
|
Depends on vercel/turborepo#5398 (and downstack) on the Turbo side. This PR makes it so the output path of Node.js entry chunks for pages is determined solely from the pathname. This isn't actually necessary for pages, but it makes for easier debugging anyway. See the Turbo PR for more details. This also changes the page structure so it also works if there is no `pages` directory. In this case, we still want to use pages' default _app, _document, and _error pages, even with existing app routes. So an empty page structure should still have an effect. ## Turbopack updates * vercel/turborepo#5415 <!-- Will Binns-Smith - Turbopack: Execution tests in node.js --> * vercel/turborepo#5461 <!-- Tobias Koppers - use a lock to ensure atomic invalidation from file changes --> * vercel/turborepo#5398 <!-- Alex Kirszenberg - Configure the path of the Node.js entry chunk --> * vercel/turborepo#5469 <!-- Tobias Koppers - allow hmr tests to correctly detect hmr event -->
### Description This PR allows configuring a specific path to Node.js entry chunks. Before, these would be generated under most of the same rules as dev chunks. However, in some cases, Next.js expects these chunks to be under a specific path. In any case, having unique chunk paths isn't particularly useful on the server-side. ### Testing Instructions N/A
### Description This PR allows configuring a specific path to Node.js entry chunks. Before, these would be generated under most of the same rules as dev chunks. However, in some cases, Next.js expects these chunks to be under a specific path. In any case, having unique chunk paths isn't particularly useful on the server-side. ### Testing Instructions N/A
### Description This PR allows configuring a specific path to Node.js entry chunks. Before, these would be generated under most of the same rules as dev chunks. However, in some cases, Next.js expects these chunks to be under a specific path. In any case, having unique chunk paths isn't particularly useful on the server-side. ### Testing Instructions N/A
Description
This PR allows configuring a specific path to Node.js entry chunks. Before, these
would be generated under most of the same rules as dev chunks. However, in some
cases, Next.js expects these chunks to be under a specific path. In any case,
having unique chunk paths isn't particularly useful on the server-side.
Testing Instructions
N/A