- 29 May, 2025 4 commits
-
-
vercel-release-bot authored
-
Jude Gao authored
-
Jude Gao authored
Since the corresponding change has been released in Vercel CLI, we can re-enable the test.
-
Jude Gao authored
Reverts vercel/next.js#77797 Reinstate the `Vary` header to prevent browsers from incorrectly reusing RSC responses during bfcache restores.
-
- 23 May, 2025 3 commits
-
-
Donny/강동윤 authored
### What? Add tests for the interestingness detection for the RC
-
Donny/강동윤 authored
### What? Fix the usefulness detector for the React Compiler ### Why? JSX was also a target of the React Compiler
-
Benjamin Woodruff authored
Without this, some files may fail to open correctly. Internal discussion: https://vercel.slack.com/archives/C07UWUAF95Z/p1747261772629689
-
- 19 May, 2025 1 commit
-
-
Hendrik Liebau authored
Backport of #79309 to 15.3.x
-
- 06 May, 2025 7 commits
-
-
vercel-release-bot authored
-
Benjamin Woodruff authored
This is a straightforward backport of https://github.com/vercel/next.js/pull/78488. There were only a few minor merge conficts. This *mostly* impacted use of Turbopack with persistent caching (which is canary-gated), but we saw some reports of it without persistent caching, so this backports the fix. Tested with ``` cargo check cargo test -p turbo-tasks-backend cargo test -p turbo-tasks-memory ```
-
JJ Kasper authored
Backport of #78261 to 15.3.x Co-authored-by:Will Binns-Smith <wbinnssmith@gmail.com>
-
JJ Kasper authored
Backport of #78874 to 15.3.x Co-authored-by:Donny/강동윤 <kdy1997.dev@gmail.com>
-
Donny/강동윤 authored
https://github.com/vercel/next.js/pull/78453 is a bugfix for sourcemap on windows
-
JJ Kasper authored
Backport of #77963 to 15.3.x Co-authored-by:Jiachi Liu <inbox@huozhi.im>
-
JJ Kasper authored
Backport of #78325 to 15.3.x
-
- 17 Apr, 2025 2 commits
-
-
vercel-release-bot authored
-
Jiachi Liu authored
-
- 16 Apr, 2025 1 commit
-
-
Donny/강동윤 authored
### What? Backport https://github.com/vercel/next.js/pull/75605 ### Why? x-ref: https://vercel.slack.com/archives/C06DGJ420TZ/p1744644426250019
-
- 15 Apr, 2025 2 commits
-
-
Steven authored
Backport of https://github.com/vercel/next.js/pull/78149 to 15.3.x
-
Steven authored
Backport of https://github.com/vercel/next.js/pull/78066 to 15.3.x --------- Co-authored-by:
Sebastian "Sebbie" Silbermann <sebastian.silbermann@vercel.com>
-
- 09 Apr, 2025 20 commits
-
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Vercel Release Bot authored
-
Tobias Koppers authored
### What? Avoid eventual consistent results influencing the map state.
-
JJ Kasper authored
We don't need to change the extension as the main fix is to ensure the `package.json` is copied to the standalone folder. The extension change was for more correctness but can cause breakage for anyone using `type: 'module'` as they will need to update their flows for the new `.mjs` extension. Since this is un-necessary breakage this reverts that piece of the fix. x-ref: https://github.com/vercel/next.js/pull/77944#discussion_r2035618277
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing alternative bundlers.
-
Vercel Release Bot authored
This auto-generated PR updates the production integration test manifest used when testing alternative bundlers.
-
Steven authored
Reverts vercel/next.js#77941
-
Niklas Mischkulnig authored
🙈 -
Andrew Clark authored
Sets up a flag that will depend on an experimental React feature (Activity). I based this on the existing code for the `viewTransition` flag. I haven't implemented anything behind this flag yet; this only wires up the flag itself. I added a basic test that renders the Activity component to verify that it's available when the flag is on.
-
Will Binns-Smith authored
Turbopack: update docs for `config.turbopack` As `turbo.mdx` is renamed to `turbopack.mdx`, we’ll need a redirect on the nextjs.org website to take users to the new location. This will be a separate PR in its repository. --------- Co-authored-by:Tim Neutkens <tim@timneutkens.nl>
-
Sebastian "Sebbie" Silbermann authored
-
Janka Uryga authored
This test flaked for me here: https://github.com/vercel/next.js/actions/runs/14353556171/job/40239845657#step:33:678 I suspect this is because \[the assertion that the pending state should disappear\] sometimes runs too soon. I made it wait until the side-effect of clicking the "debug mode" button becomes visible before checking if the pending state is gone. If this fix doesn't improve the situation, it indicates a bug in `useLinkStatus`, because the pending state is still hanging around for some reason. (i chose not to just wrap the assertion in a `retry()`, because we want to ensure that the indicator disappears immediately, not at some unspecified point in the future)
-
Tobias Koppers authored
### What? When cells are removed, dependents on these cells should be invalidated. But we want to make sure to invalidate them only once (when the cells are removed), otherwise we could end up in an invalidation cycle, since dependents are only removed when the dependent tasks is finished.
-
Jiwon Choi authored
The file tree can be improved and share the same convention: - Use the `txt` file extension. - One tab indented. - Use file tree with root `.` and trailing slash for folders. x-ref: https://tree.nathanfriend.io
-
Will Binns-Smith authored
Closes PACK-4263 This: - Adds support for using `config.turbopack` for Turbopack. The accepted value for this option is identical to the previous experimental one without the deprecated field `loaders`. - Deprecates `config.experimental.turbo`. Warns on its use, but will continue to accept it, merging it with `config.turbopack` while preferring fields on `config.turbopack`. - also see https://github.com/vercel/next.js/pull/77850#pullrequestreview-2749738760 Test Plan: - [x] Convert use of `config.experimental.turbo` in tests to `config.turbopack` - [x] Automated test for accepting the experimental option for compatibility, as well as the config merging
-
Janka Uryga authored
Adds a build script for `next-error-code-swc-plugin`, runnable via `pnpm build-error-code-plugin`. The script compiles the plugin and moves the result to its expected location in `packages/next/next_error_code_swc_plugin.wasm`. I've also rebuilt the plugin and committed it -- i was getting a different compiled output that what's currently there. Not sure if the build is non-deterministic, a dependency changed, or if someone forgot to recompile it, but it can't hurt.
-
Janka Uryga authored
Adds `useLinkStatus` to the list of APIs that can't be imported in server components.
-
Donny/강동윤 authored
### What? Fix the ES analyzer, for the case below. ```js import { assert } from "./assert"; function runGetClassesOrUseCache() { use_cache: { assert(1, 1); if (true) { break use_cache; } return "value a"; } { assert(2, 2); } assert(3, 3); return "value b"; } ``` ### Why? ### How? Fixes #77083 Closes PACK-4258 --------- Co-authored-by:Niklas Mischkulnig <4586894+mischnic@users.noreply.github.com>
-