- 11 Dec, 2025 6 commits
-
-
nextjs-bot authored
-
Hendrik Liebau authored
facebook/react#35351 Co-authored-by:Josh Story <story@hey.com>
-
nextjs-bot authored
-
Hendrik Liebau authored
Co-authored-by:Josh Story <story@hey.com>
-
Josh Story authored
-
Zack Tanner authored
* remove urlencoded server action handling (#14) * remove urlencoded server action handling * urlencoded POSTs should still flow through action handler * bailout early for urlencoded * tweak handling to 404 in feetch action case * error when there are no server actions (#15) * remove custom error * remove dev gate * error when there are no server actions * gate against dev * Check whether action ids are valid before parsing (#16) * Check whether action ids are valid before parsing In an effort to narrow access to parsing methods Next.js now prequalifies MPA form parsing by ensuring there are only valid action IDs as part of the submission. This is not meant to be a strong line of defense against malicious payloads since action IDs are not private and are for many apps relatively easy to acquire. It does however provide some limited narrowing of code paths so that action decoding only happens for plausible actions Additionally all other branches that use next-action header now consistently check the header before proceeding with parsing. This is also a perf improvement. * fix test assertion --------- Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com> --------- Co-authored-by:
Josh Story <story@hey.com>
-
- 10 Dec, 2025 1 commit
-
-
JJ Kasper authored
-
- 03 Dec, 2025 4 commits
-
-
nextjs-bot authored
-
JJ Kasper authored
-
Josh Story authored
* Update React Version Update React Version * Disable some tests that fail spuriously. Should improve test coverage of otherwise blocked tests * types are wrong
-
JJ Kasper authored
-
- 10 Oct, 2025 2 commits
-
-
Zack Tanner authored
Backports: - #84539 - #84712 --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Zack Tanner authored
[backport] fix: unstable_cache should perform blocking revalidation during ISR revalidation (#84716) Backports: - #83820
-
- 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
-