- 01 Nov, 2025 2 commits
-
-
nextjs-bot authored
-
nextjs-bot authored
-
- 31 Oct, 2025 21 commits
-
-
nextjs-bot authored
-
Zack Tanner authored
Moves `resume-data-cache` to `test/e2e`. We don't currently run `production` tests when deployed - many of them do funky things with `next.build` / `next.start` and are meant to test local behavior rather than deployed behavior. As a result, I also temporarily disabled this test when deployed because there are currently bugs.
-
Zack Tanner authored
This removes the indirection that was set up to codesplit on the client. But now that there's only a single client cache entrypoint, we can delete the indirection and move everything to a top-level export.
-
Wyatt Johnson authored
### What? This PR preserves the specific interception route markers in dynamic parameter types throughout the routing system. ### Why? Previously, the code only tracked whether a parameter was intercepted (using generic types like `'dynamic-intercepted'` or `'catchall-intercepted'`) but not which specific interception marker was used. This meant that routing information about the interception pattern was being lost. Interception routes use different markers: - `(.)` - matches segments at the same level - `(..)` - matches segments one level up - `(..)(..)` - matches segments two levels up - `(...)` - matches segments from the root app directory Without preserving the specific marker, the routing system couldn't properly distinguish between these different interception patterns, which could lead to incorrect route matching behavior. ### How? The fix encodes the specific interception marker pattern directly in the type definition. For example: - `'dynamic-intercepted'` → `'dynamic-intercepted-(.)'`, `'dynamic-intercepted-(..)'`, etc. - `'catchall-intercepted'` → `'catchall-intercepted-(.)'`, `'catchall-intercepted-(..)'`, etc. This change is propagated throughout the routing system: - Type definitions in `app-router-types.ts` and `types.ts` - Route parameter parsing in `route-params.ts` - Static path generation in `build/static-paths/app.ts` - Dynamic parameter utilities in `get-dynamic-param.ts` and `get-segment-param.tsx` - On-demand entry handling in development mode NAR-486
-
Tobias Koppers authored
### What? add a size hint to the Chunk iterator to allow optimizations
-
Shu Ding authored
Clear global data array to release memory after server data is flushed. For large apps we found that up to megabytes of data only used by hydration can be held by `window.__next_f` for the entire session.
-
Sebastian "Sebbie" Silbermann authored
Because deploy tests won't have access to the child process.
-
Hendrik Liebau authored
This PR extracts the existing git change detection logic from the `get-changed-tests` script into a separate module. This allows reusing the same logic in the `run-for-change` script, ensuring consistent behavior across the two scripts to determine changed files. Specifically, this ensures that in stacked PRs, the docs-only change detection (and the test-only change detection in the upstack PR) works correctly by diffing against the appropriate base branch.
-
Tobias Koppers authored
### What? Turbo tasks Arc should be dropped before returning to the caller
-
Benjamin Woodruff authored
Migrated from https://github.com/vercel/next.js/pull/85478 into this non-fork because we had some issues with our CI infra that should be fixed going forward: https://vercel.slack.com/archives/C04KC8A53T7/p1761862171772939 --- fixes #85474 Previously, the analyzer treated all assignment expressions the same way, evaluating them as their right-hand side value. This was incorrect for compound assignments (+=, -=, *=, |=, >>=, etc.), which compute a new value based on both the left and right operands. This commit distinguishes between simple assignments (=) and compound assignments. Simple assignments continue to evaluate to the right-hand side, while compound assignments are now properly marked as unknown values with side effects. Also adds tests for compound assignments in conditionals, covering bitshift operations (>>=, <<=, >>>=) and bitwise operations (|=, &=, ^=) with both numbers and bigints.
-
Tobias Koppers authored
### What? Fixes a deadlock due to concurrent task locks. Also adds a debug check to prevent this in future.
-
Joseph authored
Co-authored-by:vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
-
Tobias Koppers authored
### What? Enabling the feature will double execute tasks and print to stdout when tasks are updating cells while recomputing The change will also change the behavior of cell updates during recomputation slightly. Instead of updating the cell and not notifying dependents, it will not update the cell at all ignoring the (unexpected) change. This means when a task is recomputed without being invalidated, it won't update any cell data, except for the missing cell values.
-
Tobias Koppers authored
### What? Helps finding Item does not exist or access type errors
-
Tobias Koppers authored
### What? Add a few more checks when verify_serialization is enabled
-
Sebastian "Sebbie" Silbermann authored
-
Luke Sandberg authored
### What Add an option to turbopack to render sourcemap relative file paths in source maps For now this is unused since it requires some support in next to be added in #85576 ### Why This will be useful for server source maps because it enables node and other runtimes to automatically format file paths to be working directory relative when printing errors to the console which many terminal emulators support to make clickable. ### TIL My initial approach for this was to set the `sourceRoot` option to avoid prepending the same string onto nearly every source uri. However, the spec on this sourcemap feature is garbage. Intuitively i thought it worked like `<base href=...>` where relative uris would 'resolve' against it, but no, it is just a string concatenation feature. sigh.
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Zack Tanner authored
-
Zack Tanner authored
Turning this flag off would have already caused client-side invariants because we deleted all the old codepaths. This fully removes the remaining plumbing that supported the flag.
-
- 30 Oct, 2025 17 commits
-
-
nextjs-bot authored
-
JJ Kasper authored
This fixes parallel routes being considered separate outputs with the same pathname in the adapters build-complete hook and instead merges them into the same output combining the necessary outputs.
-
Benjamin Woodruff authored
Noticed this was dead while I was looking through how we might integrate bincode. We only ever use `any_serialization` and not `magic_serialization`. In theory, `magic_serialization` is slightly better because it can include the type name in the error message. If we go through with the bincode stuff, I'll replace `any_serialization` and the `MagicAny` serialization with something that doesn't depend on `erased-serde`.
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Hendrik Liebau authored
-
Tobias Koppers authored
### What? That makes a tracing look a bit better
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
Moves the assertions out of `act` and removes redundant waiting for elements. Similar to https://github.com/vercel/next.js/pull/85417
-
Tobias Koppers authored
### What? Fix Equal implementation on a bunch of structs. Make tasks deterministic
-
Luke Sandberg authored
[turbopack] Change where `cell`s are created in `resolve_raw` to make cell allocation order deterministic. (#85525) Constructing cells within a `try_flat_join` will lead to racy creation. Instead we just need to do a second pass after the fact Also eliminate a clone while we are there.
-
Hendrik Liebau authored
I noticed that we fixed some of the differences in error stacks and source frames between bundlers, which allows us to consolidate duplicate snapshots. To accomplish this, I asked Claude to write an AST-based script to find and deduplicate the affected snapshots.
-
Tobias Koppers authored
### What? Get rid of `impl Into` for value types. It's kind of legacy and we want cell creation to be kind of explicit instead of hidden in `into()` calls. Also reduces the generated code size of the macro, potentially reducing rust build time and binary size.
-
Luke Sandberg authored
[turbopack] Move generation of `cacheLife` types out of the webpack plugin and into the dev bundler directly (#85539) Ensure that users configuring custom `cacheLife` configs with Typescript get support with turbopack This follows the same pattern as typed-routes, so generation can happen during `next type-gen` and also via the dev bundler. Also this fixes a subtle bug in the timestamp formatting where we believed months had 30 or 31 _weeks_ instead of 30 or 31 _days_s. Beyond the unit tests, i also tried out adding a `cacheLife` config to the `with-turbopack` example and observed that the types were generated and vscode was able to autocomplete my custom config type. Fixes NAR-458
-
Sebastian "Sebbie" Silbermann authored
-