- 04 Nov, 2025 18 commits
-
-
nextjs-bot authored
-
Benjamin Woodruff authored
This syntax isn't needed in modern rust. https://doc.rust-lang.org/reference/names/preludes.html#extern-prelude > Beginning in the 2018 edition, use declarations can reference crates in the extern prelude, so **it is considered unidiomatic to use extern crate**.
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing Rspack.
-
Niklas Mischkulnig authored
Closes PACK-5688 Closes https://github.com/vercel/next.js/issues/84766 1. Trace `new require("worker_threads").Worker` calls 2. ignore syntax errors in all traced files This does lead to a build error currently with cargo run --bin turbopack-nft -- --show-issues --graph bench/app-router-server/node_modules/thread-stream/index.js: ``` error - [analysis] [workspace]/node_modules/.pnpm/thread-stream@3.1.0/node_modules/thread-stream/test/syntax-error.mjs [workspace]/node_modules/.pnpm/thread-stream@3.1.0/node_modules/thread-stream/test/syntax-error.mjs:2:6 Parsing ecmascript source code failed 1 | // this is a syntax error + v 2 + import + ^ 3 | Expected 'from', got '<eof>' ``` Pulled in by this partly dynamic `new Worker()` call: https://github.com/pinojs/thread-stream/blob/82e011281b8895bf5e8f70008e0242927fcaf0cb/index.js#L53-L55 (Related to https://github.com/vercel/next.js/pull/84408, where this was previously fixed for extensionless files such as `LICENSE`)
-
Cong-Cong Pan authored
1. Fixed the incremental update bug in buildChunkGraph. 2. Fixed a bug in Rspack's built-in CssChunkingPlugin. For detailed release information, please see https://github.com/web-infra-dev/rspack/releases.
-
nextjs-bot authored
-
Jiwon Choi authored
`eslint-config-next` types were being emitted to `dist/src` instead of `dist/` during build. | Before | After | |--------|--------| | <img width="422" height="452" alt="CleanShot 2025-11-04 at 15 50 38@2x" src="https://github.com/user-attachments/assets/09c96d1a-41ba-4da9-87c6-bc05257c6e2a" /> | <img width="386" height="488" alt="CleanShot 2025-11-04 at 15 50 01@2x" src="https://github.com/user-attachments/assets/7b9802a4-e453-4086-90fb-a19e1aec7e20" /> | Fixes https://github.com/vercel/next.js/issues/85379 Closes: https://github.com/vercel/next.js/pull/84929 Closes: https://github.com/vercel/next.js/pull/85653
-
Niaz Morshed Nayeem authored
### What? Fix documentation typo in `refresh` function.
-
Joseph authored
Prepping for a bit more helpful work with these matchers
-
Tim Neutkens authored
## What? Fixes a small retainer object that is inserted on each request and not cleaned up. While at it also swapped array -> Set for the type checks to leverage `has` instead of `includes`.
-
Sebastian "Sebbie" Silbermann authored
-
Joseph authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
nextjs-bot authored
[diff facebook/react@561ee24d...67f7d47a](https://github.com/facebook/react/compare/561ee24d...67f7d47a) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/35036 </details>
-
Niklas Mischkulnig authored
We had tree shaking enabled for NFT. That is incorrect however, as even unused imports (if you don't use any of the imported bindings, and the file is marked as `sideEffects: false`) are still needed at runtime, since Node.js will execute everything anyway. - I made the `treeShakingMode: None` explicit now (though that was already the `Default::default` anyway) - The real problem was that we still dropped side-effect free `ModulePart::Evaluation` references even when tree shaking was disabled. Closes #85172 Fixes PACK-5756
-
Niklas Mischkulnig authored
This abstraction was a leftover from when we had a swc_css and a lightningcss backend. Also inspired by https://github.com/vercel/next.js/pull/85524 as there was another constant-false `PartialEq` impl.
-
- 03 Nov, 2025 18 commits
-
-
nextjs-bot authored
-
Tan Zi Gang authored
Fix #85715 --------- Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by:
Jiwon Choi <devjiwonchoi@gmail.com>
-
Jiwon Choi authored
Codemod `next-lint-to-eslint-cli` did not handle `extends: ['next']` in legacy ESLint config. x-ref: https://github.com/vercel/next.js/issues/85244#issuecomment-3482558412 Fixes #85244
-
ajstrongdev authored
### What? - Add mention of ESLint being the default linter when specifying `--yes` flag on `create-next-app` ### Why? - Adds consistency by calling out the default linter. Co-authored-by:Joseph <joseph.chamochumbi@vercel.com>
-
Sebastian "Sebbie" Silbermann authored
Suspecting that this fixes (or reduces) the "Watchpack Error (watcher): Error: EMFILE:" issues e.g. https://github.com/vercel/next.js/actions/runs/19028750529/job/54337767548?pr=85637 I noticed that all the Watchpack errors in CI happened in tests with a tsconfig (or ones where a tsconfig was created). When watchpack starts watching, an initial `aggregated` event is set. During that event we used to consider all files as changed because we hadn't seen them before. This also meant we considered the tsconfig as changed and invalidated the hot-reloader. This is excessive and likely hits some hard to debug race conditions. Now we check if the file was actually changed since we started watching by comparing its change time to the time when we started watching. Each file modified before we started watching is no longer considered changed.
-
Sebastian "Sebbie" Silbermann authored
Fixes https://github.com/vercel/next.js/actions/runs/18937795131/job/54068900147#step:34:1879 `--experimental-https` test creates a cert relying on no cert existing in the default path. When it passes, it doesn't cleanup. Retrying that test file due to an unrelated failure would therefore always fail. Now we ensure no cert exists.
-
Hendrik Liebau authored
[flakiness metric](https://app.datadoghq.com/ci/test/runs?query=test_level%3Atest%20%40git.repository.id%3A%22github.com%2Fvercel%2Fnext.js%22%20%40test.name%3A%22use-cache-custom-handler%20should%20use%20a%20modern%20custom%20cache%20handler%20if%20provided%22%20%40test.type%3A%22nextjs%22%20%40test.status%3A%22fail%22%20%40git.branch%3Acanary&agg_m=count&agg_m_source=base&agg_t=count&fromUser=true&index=citest&start=1759310750664&end=1761902750664&paused=false) The test page used a low revalidate time of 3 seconds. In CI, sometimes that much time passes between the first and second request, causing the test to fail when comparing the data values (locally reproducible with `{ cpuThrottleRate: 20 }`). Increasing the revalidate time to 6 seconds should make the test more robust.
-
Sebastian "Sebbie" Silbermann authored
-
Joseph authored
-
Tobias Koppers authored
### What? Makes adding multiple items at once more efficient.
-
Vercel Release Bot authored
This auto-generated PR updates font data with latest available
-
Sebastian "Sebbie" Silbermann authored
-
Jiachi Liu authored
In v16, `id` argument in metadata routes becomes promise which requries to to unwrap it first to access the value Follow up of #84491 Closes #85632 --------- Co-authored-by:Joseph Chamochumbi <joseph.chamochumbi@vercel.com>
-
Tim Neutkens authored
## What? Upgrade the image crate which includes some bugfixes for bmp files.
-
Marjan Ahmed authored
### What? Fixes an inconsistency in the v16 upgrade documentation for `generateImageMetadata`. ### Why? In the “Upgrading to Version 16” guide, the example incorrectly awaited the `params` object inside `generateImageMetadata`, implying that it was a Promise. However, according to the API reference, `params` is a normal object. This PR updates the example to reflect the correct synchronous usage. ### How? Replaced: ```ts export async function generateImageMetadata({ params }) { const { slug } = await params return [{ id: '1' }, { id: '2' }] } With ```ts export async function generateImageMetadata({ params }) { // params is a normal object return [{ id: '1' }, { id: '2' }] } --------- Co-authored-by:Joseph <joseph.chamochumbi@vercel.com>
-
Sebastian "Sebbie" Silbermann authored
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing Rspack.
-
Vercel Release Bot authored
This auto-generated PR updates the production integration test manifest used when testing Rspack.
-
- 02 Nov, 2025 4 commits
-
-
nextjs-bot authored
-
Vercel Release Bot authored
This auto-generated PR updates the production integration test manifest used when testing Rspack.
-
Jiwon Choi authored
The heading sections in DevTools regressed. We decided to remove them as "Dev Server" settings are obviously dev server settings, no need to differentiate as separate tabs. | Before | After | |--------|--------| | <img width="1024" height="1006" alt="CleanShot 2025-11-02 at 12 59 21@2x" src="https://github.com/user-attachments/assets/0a8b0c2f-3f0a-487d-9344-b33b5ee016f5" /> | <img width="1024" height="1006" alt="CleanShot 2025-11-02 at 12 59 07@2x" src="https://github.com/user-attachments/assets/ddd3b029-8957-4129-aaf2-7b1a57a52e00" /> |
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing Rspack.
-