- 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 27 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>
-
Tobias Koppers authored
### What? Allow to search for attribute name and name value pair
-
Tobias Koppers authored
### What? When a Turbopack build finishes with a crash and throws an error, we still want to make sure to gracefully shutdown turbo tasks. This ensures that cache and trace is written correctly.
-
Gengkun authored
This version has some fixes for the communication issues between Rust and JS, which can prevent next-rspack from being ridiculously slow in real-world projects. <!-- 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 # --> --------- Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Will Binns-Smith authored
This: - Tracks build failures as a separate event, `NEXT_BUILD_FAILED` - Added `bundler` property to both `NEXT_BUILD_COMPLETED` and `NEXT_BUILD_FAILED` - Requires a server-side update Alternatives considered: Considered adding a `success: boolean` property to the existing `EventBuildCompleted`. There are a few issues with this: - Expands the semantics of the existing event. This may have unintended consequences if we don’t change how we report on these events to filter success state - This event requires page paths and timing information from the compiler, neither of which are guaranteed to exist on failures Test Plan: - Added a syntax error to a module and built with `NEXT_TELEMETRY_DEBUG=1`. Verified the failure event is sent along with the bundler value - Verified bundler values are now sent for webpack, rspack, and Turbopack on build successes
-
Will Binns-Smith authored
-
Kain authored
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing alternative bundlers.
-
- 08 Apr, 2025 1 commit
-
-
vercel-release-bot authored
-