- 11 Jun, 2025 12 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
This continues the `handler` signature work from https://github.com/vercel/next.js/pull/78166 and moves the cache/response handling work inside of the pages, app pages, and app route handlers which allows them to be fully invoked independent of `next-server`/`router-server`. Validated against our deploy tests https://github.com/vercel/vercel/actions/runs/15583209888/job/43883202911?pr=13433 and https://github.com/vercel/next.js/actions/runs/15583265934/job/43883389321
-
Delba de Oliveira authored
Closes: - https://github.com/vercel/next.js/issues/76573 - https://github.com/vercel/feedback/issues/97181 - https://github.com/vercel/feedback/issues/96268 - https://github.com/vercel/feedback/issues/95318 - https://github.com/vercel/feedback/issues/95317 - https://github.com/vercel/feedback/issues/93861 - https://github.com/vercel/feedback/issues/91802 - https://github.com/vercel/feedback/issues/97192 --------- Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
-
Jiachi Liu authored
Unflake turbopack dev test ``` pnpm test-dev-turbo test/e2e/app-dir/actions/app-action.test.ts (turbopack) app-dir action handling > should forward action request to a worker that contains the action handler (node) app-dir action handling > should forward action request to a worker that contains the action handler (edge) ``` x-ref: https://github.com/vercel/next.js/actions/runs/15581296918/job/43881444430?pr=80392
-
Hendrik Liebau authored
In e2e tests, we sometimes want to assert on the response headers and on the rendered HTML within the same test. For the former, we usually use `next.fetch()`, but this doesn't allow us to use the Playwright browser API to assert on the rendered HTML, which is available through `next.browser()`. This is especially tricky when a PPR shell is resumed, where asserting on the response text is error-prone, as the streamed-in HTML may change the elements that we want to assert on. To avoid the maintenance and runtime overhead of splitting the test into two separate tests, we introduce a new `next.browserWithResponse()` method that allows us to use the Playwright browser API while also exposing the response to check the headers and other properties. --------- Co-authored-by:Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
Vercel Release Bot authored
-
Vercel Release Bot authored
-
Vercel Release Bot authored
-
Vercel Release Bot authored
-
Luke Sandberg authored
On its own this is just adding pure overhead. The next step will be to make it _optional_ for a value_trait item to be a turbo-tasks function. Part of PACK-4560
-
Delba de Oliveira authored
Closes: https://github.com/vercel/next.js/issues/78255 --------- Co-authored-by:
Joseph <joseph.chamochumbi@vercel.com>
-
Donny/강동윤 authored
### What? ChangeLog: https://github.com/swc-project/swc/compare/swc_core%40v26.4.4...swc_core%40v27.0.1 ChangeLog for plugins: https://github.com/swc-project/plugins/pull/466 ### Why? Apply `swc_sourcemap` performance optimization.
-
- 10 Jun, 2025 28 commits
-
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? We didn't include already removed entries in the usage computation. So a meta file was incorrectly marked as unused and was removed.
-
Benjamin Woodruff authored
fix(next-swc-wasm): Only enable turbo-rcstr's napi feature when building the next-swc-napi crate/package (#80390) Fixes https://vercel.slack.com/archives/C04KC8A53T7/p1749584921462879 ``` pnpm swc-build-wasm ```
-
Hendrik Liebau authored
When a cache handler returns `Infinity` from its `getExpiration` method, it signals to Next.js that soft/implicit tags are supposed to be passed into the `get` method instead to be checked for expiration. Documenting this in the `CacheHandlerV2` interface, and always passing in the soft tags was implemented in #79213. However, we missed handling the infinite expiration value, which led to regarding all cache entries returned from those cache handlers as stale. The first commit provokes the error, the second commit fixes it. We'll also soon (re-)add proper deploy tests that will verify scenarios like this one end-to-end when deployed to Vercel. /cc @laugharn
-
Sebastian "Sebbie" Silbermann authored
pages/ and app/ now have a designated "setup" file. Makes it easier to spot their differences. The error handling would ideally be the same between App and Pages router but it's unlikely we'll have time porting the new App Router goodies with regards to error reporting to Pages Router.
-
vercel-release-bot authored
-
Sebastian "Sebbie" Silbermann authored
Best reviewed without whitespace changes.
-
Joseph authored
Closes: https://linear.app/vercel/issue/DOC-4751/docs-missing-middleware-caching-information-also-ts-types-issue Fixes: https://github.com/vercel/next.js/issues/77900 Note that the TypeScript (should the TS plugin detect fetch `options.next` used in middleware and error out?) issue is still pending. It will be eventually handled.
-
Sebastian "Sebbie" Silbermann authored
The hot-reloader logic will remain outside of the upcoming `next-devtools` folder. We're shipping the org chart.
-
Sebastian "Sebbie" Silbermann authored
This doesn't properly work with if a different Chrome release channel is used. It opens Chrome stable even if I have Beta as my default. It's also annoying if you restart it and have a tab already open in you non-default browser. We don't open a browser in Next.js for those same reasons. Storybook will display a URL to click in the terminal so all this adds is one click if you start it for the first time.
-
Janka Uryga authored
We implement the behavior of `import 'server-only'` and `import 'client-only'` on the compiler level and thus don't require having them installed as dependencies. By default it works fine with typescript, because (surprisingly) TSC *doesn't check side-effecting imports*. But this behavior can be overridden with [`noUncheckedSideEffectImports`](https://www.typescriptlang.org/tsconfig/#noUncheckedSideEffectImports) which'd cause `import 'server-only'` to start erroring. To prevent that, we add declarations for them in next's global type declarations.
-
Joseph authored
Fixes a couple of broken links in caching.
-
Sebastian "Sebbie" Silbermann authored
Adds labels to buttons that had no discernible text. The automated tests via `test-storybook` seem to ignore `parameters.a11y.config.rules` so we can't leverage `test-storybook` in CI. I can't even use `parameters.a11y.test`. We need `parameters.a11y.config.rules` since some of the color-contrast violations are either minor (just slightly below threshold) or false-positives either because our background is misconfigured in automated tests, or background is not detected properly.
-
Jiachi Liu authored
-
Sebastian "Sebbie" Silbermann authored
[devtools] Implement default `/.well-known/appspecific/com.chrome.devtools.json` endpoint in dev (#80260)
-
Sebastian "Sebbie" Silbermann authored
Can be disorienting if more focusable content is added. See https://dequeuniversity.com/tips/tabindex-positive-numbers
-
Jiachi Liu authored
-
Delba de Oliveira authored
To do: - [x] Triggering unwanted side-effects during prefetching - @delbaoliveira - [x] Preventing too many prefetches - @delbaoliveira - [x] Disabling prefetching on hover - @icyJoseph - [x] Ejected link - soft navigation with `onClick` and `router.push` - @icyJoseph --------- Co-authored-by:
Joseph <joseph.chamochumbi@vercel.com> Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by:
Lee Robinson <lee@leerob.com>
-
Sebastian "Sebbie" Silbermann authored
A bit annoying that Storybook marks required props as optional. Makes it hard to keep those working during refactor.
-
Delba de Oliveira authored
Part of: https://linear.app/vercel/issue/DOC-4686/clean-up-routing-section --------- Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
-
Delba de Oliveira authored
Closes: https://linear.app/vercel/issue/DOC-4678/guide-data-security Please merge this PR first: https://github.com/vercel/next.js/pull/80242 --------- Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by:
Joseph <joseph.chamochumbi@vercel.com>
-
Sebastian "Sebbie" Silbermann authored
Broke in https://github.com/vercel/next.js/pull/79699
-
Sebastian "Sebbie" Silbermann authored
-
Joseph authored
Closes: #80346 - https://github.com/vercel/next.js/blob/2f63e47d739dd9f70c93c68f2d3b6a582595c498/packages/next/src/server/lib/patch-fetch.ts#L807-L812 - https://github.com/vercel/next.js/blob/2f63e47d739dd9f70c93c68f2d3b6a582595c498/packages/next/src/server/lib/incremental-cache/index.ts#L417-L426
-
Jiachi Liu authored
### What When there's a same error throwing constantly, we should avoid unnecessary re-renders on the exact same error. In dev overlay we already have strategies that can dedupe the error. And we noticed the error is shown correctly but just the dialog got re-rendered with animations. After digging deeper, noticed we are still adding the same runtime error into the error collection, just because each time it got the new "ID", as the "ID" itself is incremental based on actions. Each action will get a new error ID. Hence we're adding a condition in deduping. If we found that the new error already existed in the previous events, we'll return with the same previous events instance to tell dev overlay that errors are not changed. Fixes NEXT-4493 #### After https://github.com/user-attachments/assets/c1f004b5-2de6-445a-aad0-efdfd0ecb8c9 #### Before https://github.com/user-attachments/assets/1249ed54-ba63-4eb6-a08a-64560ab4014a
-
Vercel Release Bot authored
-
Vercel Release Bot authored
-