- 11 Dec, 2025 4 commits
-
-
vercel-release-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> * fix test --------- Co-authored-by:
Josh Story <story@hey.com>
-
- 03 Dec, 2025 5 commits
-
-
vercel-release-bot authored
-
JJ Kasper 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
-
- 08 Apr, 2025 7 commits
-
-
vercel-release-bot authored
-
Donny/강동윤 authored
Use `rayon` for parallelism `chili` seems to have some bugs regarding the CPU usage of heartbeat thread in idle mode. - Closes https://github.com/vercel/next.js/issues/77192
-
Donny/강동윤 authored
### What? Applies https://github.com/swc-project/swc/pull/10221 ### Why? To allow TypeScript nodes from the minifier.
-
Donny/강동윤 authored
### What? Applies https://github.com/swc-project/swc/pull/10196 ### Why? https://github.com/swc-project/swc/pull/10196 makes minification 3%~4% faster
-
Jiachi Liu authored
Upgrade the `@vercel/og` patch to Next.js which will resolve the build issue on windows. Closes NEXT-4069 Related #77164 Related: https://github.com/nodejs/nodejs.org/issues/7438
-
Jude Gao authored
Follow-up to https://github.com/vercel/next.js/pull/76976 Since we want to make explicit mode check from outside, we can now remove the implicitly checked one from inside.
-
Jiachi Liu authored
### What While adding a regression test for overlay JS bundle to ensure it's not gonna existed in client bundles by asserting the source map. Found that we're also including the indicator reducer from client JS bundles. This PR ensure we fully strips it out
-
- 24 Mar, 2025 6 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
This aligns our subrequest handling between edge and node runtimes as we did not carry over this handling for node and as such we want to remove this from edge as well.
-
Zack Tanner authored
Excludes `/_next/image` and `/_next/static/media` as they don't contain sensitive information and prevents complications loading them in cases where they are inlined in CSS, as they'll be requested with `sec-fetch-mode: no-cors`. x-ref: https://github.com/vercel/next.js/issues/77344
-
Zack Tanner authored
We have special development endpoints that are also prefixed under `/__nextjs`. This updates the origin checking logic to account for those in addition to `/_next`, and adds a test.
-
Zack Tanner authored
It's potentially unsafe to allow any sort of origin bypass if `allowedDevOrigins` is configured as it's trivial to stand up a remote server on the same port. This removes the case that would bypass the origin check.
-
Zack Tanner authored
To avoid breaking local development proxies and more complex setups, this ensures that we only block cross-origin development requests when opting into the configuration. In a future major release, this will not be opt-in, and will require explicitly providing the allowed origins that can access the special `/_next` endpoints. This adds a warning when a cross origin request is detected that would be blocked without explicit configuration. Fixes #77073 Fixes #77253 Fixes #77344
-
- 17 Mar, 2025 9 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
Per feedback in https://github.com/vercel/next.js/pull/76880 this ensures we ocnsider `*.localhost` as allowed by default for the dev origins list.
-
Zack Tanner authored
This unifies the CSRF origin detection to mirror what we do for server action origins, which supports things like wildcard matches (below the domain level) Fixes #76999
-
JJ Kasper authored
Adding a warning when we block cross-origin requests in dev so users are aware this is why easier and know how to allow the origin through as custom setups can use different origins and it be valid. x-ref: https://github.com/vercel/next.js/pull/76880#issuecomment-2718487112 --------- Co-authored-by:
Jiachi Liu <inbox@huozhi.im> Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
JJ Kasper authored
This just ensures we use the deployment ID if configured for preload CSS links. x-ref: [slack thread](https://vercel.slack.com/archives/C03S8ED1DKM/p1742146672858189)
-
JJ Kasper authored
This just adds an additional header to our internal filtering list for middleware.
-
Jiachi Liu authored
### What Remove the default segment checks for metadata rendering. When the `default.js` is rendered, it should still have the metadata. It was a condition added due to possible of duplicated metadata, but it's resolved by other conditions such as only rendering in child slot, and hoisting metadata into rsc head for navigation.
-
Jiachi Liu authored
### What Fix the enabling of ts hint plugin in vscode. This is a regression introduced in #76300, where we use the plugin config `{ "name": "next" }` to directly check if it has a `enabled` property, and determine if we should enable the plugin. This PR fixed the way of reading plugin config and keep it enabled by default. Fixes 76980 -
Jiachi Liu authored
### What Re-insert the metadata icons under body tag into head tag to ensure they can be proper displayed. ### Why * For chromium based browsers (Chrome, Edge, etc.) and Safari, icons need to stay under `<head>` to be picked up by the browser. Firefox doesn't have this requirement. * Firefox will always render svg > icon > png, so it doesn't matter to it. Made a test in https://icons-order-test.vercel.app/, you can play with the test cases here. These links can see the comparsion of the approach in the this PR. During deployment it's very hard to verify Safari as it's pretty broken. But deploymet works well. After we re-insert the icon from body into head, they can be properly displayed across all the browsers. Note: We insert the script during streaming rather than using a jsx element right after metadata to avoid the hydration errors Closes #76810 Closes NDX-951
-
- 11 Mar, 2025 2 commits
-
-
vercel-release-bot authored
-
Jiachi Liu authored
-
- 09 Mar, 2025 3 commits
-
-
vercel-release-bot authored
-
Oscar authored
-
Sebastian "Sebbie" Silbermann authored
-
- 08 Mar, 2025 3 commits
-
-
vercel-release-bot authored
-
Sebastian "Sebbie" Silbermann authored
-
Sam Ko authored
## Why? We're missing some still! - Add `After`, `Connection`, `Cookies`, `Headers` - Remove `Package Managers`
-
- 07 Mar, 2025 1 commit
-
-
vercel-release-bot authored
-