- 18 Aug, 2025 2 commits
-
-
nextjs-bot authored
-
Zack Tanner authored
Backports: - #82588 Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
- 06 Aug, 2025 2 commits
-
-
nextjs-bot authored
-
Jiwon Choi authored
Backports #82384 Co-authored-by:Steven <steven@ceriously.com>
-
- 05 Aug, 2025 1 commit
-
-
Jiwon Choi authored
…o dynamic param on minimal mode (#82347)" Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
- 29 Jul, 2025 8 commits
-
-
nextjs-bot authored
-
JJ Kasper authored
-
Zack Tanner authored
Backports: - #82118 Co-authored-by:Steven <steven@ceriously.com>
-
Zack Tanner authored
Backports: - #82114 Co-authored-by:Steven <steven@ceriously.com>
-
Benjamin Woodruff authored
We're heard about significant real-world reductions in memory usage from this change in canary. It seem relatively low-risk, so IMO we should backport it. Original PR: https://github.com/vercel/next.js/pull/81993Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com>
-
JJ Kasper authored
Backports https://github.com/vercel/next.js/pull/82160 to our next-15-4 release branch
-
JJ Kasper authored
This backports https://github.com/vercel/next.js/pull/82161 to our next-15-4 release branch
-
JJ Kasper authored
This backports https://github.com/vercel/next.js/pull/82136 to our next-15-4 release branch
-
- 25 Jul, 2025 1 commit
-
-
JJ Kasper authored
Backports API stripping JSON fix to 15.4 branch x-ref: https://github.com/vercel/next.js/pull/82061
-
- 24 Jul, 2025 4 commits
-
-
nextjs-bot authored
-
JJ Kasper authored
-
Niklas Mischkulnig authored
-
Niklas Mischkulnig authored
So what do we need to do about https://github.com/swc-project/swc/pull/10813? Not sure when we'd call `global_atom_store_gc()` https://vercel.slack.com/archives/C03EWR7LGEN/p1752228740427529 The 2s-debounced gc calls didn't have a measurable effect on `next build --turbo`: ``` with gc: 360.90s user 80.74s system 688% cpu 1:04.15 total 357.24s user 82.61s system 664% cpu 1:06.23 total without gc: 360.51s user 80.48s system 698% cpu 1:03.16 total 355.21s user 79.99s system 667% cpu 1:05.18 total ``` - [x] ~~Blocked on https://github.com/swc-project/swc/pull/10878~~ - [ ] https://github.com/swc-project/swc/issues/10930 Closes https://github.com/vercel/next.js/issues/81898
-
- 22 Jul, 2025 4 commits
-
-
Benjamin Woodruff authored
-
Jiachi Liu authored
-
nextjs-bot authored
-
Niklas Mischkulnig authored
-
- 18 Jul, 2025 1 commit
-
-
nextjs-bot authored
-
- 17 Jul, 2025 2 commits
-
-
Zack Tanner authored
When we updated `experimental.strictNextHead` to be true in #65418, we did not update all spots that would default to true in the case where the value was omitted entirely. This led to the default value not being correctly applied in pages router, which resulted in duplicate metadata w/ React 19. Since we made the flag the default, we can also probably clean up this flag all together, but that can be done separately. Fixes #81655 Fixes #81689
-
Jiachi Liu authored
-
- 15 Jul, 2025 2 commits
-
-
JJ Kasper authored
This ensures if using NextServer or a custom-server directly we honor the custom config passed in correctly. Backports to next-15-4 branch
-
nextjs-bot authored
-
- 14 Jul, 2025 13 commits
-
-
nextjs-bot authored
-
nextjs-bot authored
-
nextjs-bot authored
-
Luke Sandberg authored
[turbopack] Rename `traverse_edges_from_entries_topological` to `traverse_edges_from_entries_dfs` (#81481) ## Rename `traverse_edges_from_entries_topological` to `traverse_edges_from_entries_dfs` This PR renames the `traverse_edges_from_entries_topological` method to `traverse_edges_from_entries_dfs` to better reflect its actual behavior. The method performs a depth-first search traversal rather than a topological sort. The PR also: - Updates the method documentation to clarify that it performs a DFS traversal - Makes `ClientReferenceMapType` derive `Copy` for better ergonomics - Removes unnecessary `ResolvedVc::upcast` call in client references mapping - Renames some variables for clarity (`actions` → `client_references`) - Removes unused `module_graph_for_entries` function - Adds some tests for the traversal routine. Not very interesting for this traversal but should make it easier to test future traversals. These changes improve code clarity and correctness by ensuring the method name accurately describes its behavior.
-
Benjamin Woodruff authored
It should be equivalent, but it's clearer that the LHS is always visited
-
Steven authored
This fixes a handful of issues including: - https://github.com/lovell/sharp/issues/4393 - https://github.com/lovell/sharp/issues/4382 - https://github.com/lovell/sharp/issues/4398 - https://github.com/lovell/sharp/issues/4374 - https://github.com/lovell/sharp/issues/4417 See full list of changes https://github.com/lovell/sharp/compare/v0.34.1...v0.34.3
-
Benjamin Woodruff authored
Previously this was only parsing the first line of input ``` cargo run -p swc-ast-explorer <turbopack/crates/turbopack-tests/tests/snapshot/comptime/assignment/input/index.js | less ```
-
Jiachi Liu authored
-
Jiachi Liu authored
-
Joseph authored
Closes: [DOC-4741](https://linear.app/vercel/issue/DOC-4741/document-oninvalidate-for-userouter-hook)
-
Jude Gao authored
This PR fixed two typos that affected isHeadPartial logic.
-
Delba de Oliveira authored
Updates the docs to include the new options in 15.4. - `prefetch="auto"` option: https://github.com/vercel/next.js/pull/78689 - `next build` new `--debug-prerender option`: https://github.com/vercel/next.js/pull/80667 --------- Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
-
Sebastian "Sebbie" Silbermann authored
-