- 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
-
JJ Kasper authored
-
- 17 Oct, 2025 2 commits
-
-
nextjs-bot authored
-
Niklas Mischkulnig authored
Backport https://github.com/vercel/next.js/pull/83452
-
- 16 Oct, 2025 1 commit
-
-
Niklas Mischkulnig authored
Was fixed on canary in #84922 Very annoying test setup
-
- 13 Oct, 2025 1 commit
-
-
nextjs-bot authored
-
- 11 Oct, 2025 1 commit
-
-
Jiwon Choi authored
backports #82814
-
- 10 Oct, 2025 3 commits
-
-
Joseph authored
Additional group of docs improvements. --------- Co-authored-by:
François Martin <f.martin@fastmail.com> Co-authored-by:
liketiger <50165633+liketiger@users.noreply.github.com> Co-authored-by:
Milancen123 <122306536+Milancen123@users.noreply.github.com> Co-authored-by:
geraldochristiano <68152918+geraldochristiano@users.noreply.github.com> Co-authored-by:
JJ Kasper <jj@jjsweb.site> Co-authored-by:
Anshuman Bhardwaj <anshu5074@gmail.com> Co-authored-by:
Karl Horky <karl.horky@gmail.com> Co-authored-by:
João Henrique <117238473+joao4xz@users.noreply.github.com> Co-authored-by:
vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
-
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
-
- 08 Oct, 2025 1 commit
-
-
Jiwon Choi authored
This PR backports #84168
-
- 30 Sep, 2025 1 commit
-
-
Jiwon Choi authored
backports #84174
-
- 23 Sep, 2025 2 commits
-
-
nextjs-bot authored
-
Joseph authored
Collects a bunch of docs improvements and fixes. --------- Co-authored-by:
Lee Robinson <lee@leerob.com> Co-authored-by:
Felix Shih <25448040+fufuShih@users.noreply.github.com> Co-authored-by:
Benjamin Woodruff <benjamin.woodruff@vercel.com> Co-authored-by:
David <75678655+dwrth@users.noreply.github.com> Co-authored-by:
Aymeric PINEAU <62554073+aymericzip@users.noreply.github.com> Co-authored-by:
Luca Krebs <41986129+obendev@users.noreply.github.com> Co-authored-by:
vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by:
Rich Haines <hello@richardhaines.dev> Co-authored-by:
Mohammad Nedaeifard <46691519+OoMNoO@users.noreply.github.com> Co-authored-by:
pontasan <48611107+pontasan@users.noreply.github.com> Co-authored-by:
Steven <steven@ceriously.com> Co-authored-by:
Honda Yuto <132035494+HondaYt@users.noreply.github.com> Co-authored-by:
Jiachi Liu <inbox@huozhi.im> Co-authored-by:
ryu <114303361+ryuapp@users.noreply.github.com> Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by:
Lorenzo Palmes <lpalmes@gmail.com> Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
- 22 Sep, 2025 2 commits
-
-
Jiwon Choi authored
backports https://github.com/vercel/next.js/pull/83194
-
Niklas Mischkulnig authored
-
- 19 Sep, 2025 2 commits
-
-
Jiwon Choi authored
Backports #83981
-
Jiwon Choi authored
backports #83571
-
- 17 Sep, 2025 4 commits
-
-
Niklas Mischkulnig authored
-
Niklas Mischkulnig authored
-
Niklas Mischkulnig authored
Co-authored-by:Luke Sandberg <lukesandberg@users.noreply.github.com>
-
Niklas Mischkulnig authored
Co-authored-by:Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
- 15 Sep, 2025 1 commit
-
-
Niklas Mischkulnig authored
Backport #83176
-
- 12 Sep, 2025 2 commits
-
-
Jiachi Liu authored
-
yiminghe authored
Co-authored-by:Jiachi Liu <inbox@huozhi.im>
-
- 10 Sep, 2025 1 commit
-
-
nextjs-bot authored
-
- 08 Sep, 2025 1 commit
-
-
Ben Gubler authored
I don't think this fix ever got backported to Next 15.5! @huozhi @ijjk @ztanner
-
- 29 Aug, 2025 2 commits
-
-
Ben Gubler authored
Fixed #83063 - **Problem**: `next dev` produced overly deep relative imports in `validator.ts` that differed from `next typegen`/`next build`. - **Cause**: Dev pre-relativized page file paths and didn’t pass `validatorFilePath`, causing incorrect relative path computation. - **Solution**: - Pass `validatorFilePath` to `createRouteTypesManifest` in dev. - Stop pre-relativizing file paths; provide absolute `fileName` so the manifest computes paths relative to the validator directory. - **Result**: `validator.ts` now uses correct, shallow relative imports, matching `next typegen` and `next build`. - **Verification**: Reproduced with `test/e2e/app-dir/typed-routes-validator`; outputs from `pnpm next dev` and `pnpm next typegen` now match. ### Example Before (next dev): ```typescript // Validate ../../../../../../app/page.tsx { const handler = {} as typeof import("../../../../../../app/page.js") handler satisfies AppPageConfig<"/"> } ``` After (next dev/typegen/build): ```typescript // Validate ../../app/page.tsx { const handler = {} as typeof import("../../app/page.js") handler satisfies AppPageConfig<"/"> } ``` <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> -
Ben Gubler authored
[backport] fix: remove `satisfies` keyword from type validation to preserve old TS compatibility (#83071)
-
- 26 Aug, 2025 2 commits
-
-
nextjs-bot authored
-
Zack Tanner authored
Backports: - #83062
-