- 10 Jun, 2025 31 commits
-
-
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
-
Vercel Release Bot authored
-
Vercel Release Bot authored
-
Vercel Release Bot authored
-
vercel-release-bot authored
-
Donny/강동윤 authored
### What? Restore the `sources` field by picking up https://github.com/kdy1/rust-sourcemap/commit/27e1bf8b92498425fbc6e2f31d2f755b6ae94f19 ### Why? It's expected to be exist
-
Donny/강동윤 authored
### What? Utilize _cheap clone_ of `bytes::Bytes`. I made an error in the previous pull request. ### Why? - In the name of the performance. - `bytes::Bytes` is cheap to clone.
-
Benjamin Woodruff authored
This is intended as a band-aid "fix" for persistent caching where issues stick around after restarts of the development server. It builds on top of the same codepath we're using for the explicit cache clearing button in the devtools. As part of this work, this adds a centralized registry for dynamically-registered panic hooks. ## Notes & Next Steps - I'll disable this behavior for Vercel employees in front, so that we continue to get valuable bug reports. - I'll follow up with some warning message in the terminal so that the subsequent restart of `next dev` will warn the user that the persistent cache was cleared and that's why build may be slow. - We've got a some in-progress work handed to me from @wbinnssmith for better logging of anonymized (uncaught) panics to telemetry, so that should be useful in cases like this. - Yes, this will still invalidate the cache on caught panics. I'm not 100% sure that's the behavior we want, but I think it is. ## Test Plan Built with: ``` pnpm pack-next -p ~/front/apps/vercel-site cd ~/front pnpm i pnpm turbo --filter=vercel-site dev ``` Restarted a few times and looked at the persistent cache files and saw that they keep accumulating. Then, deleted a random `.sst` file, restarted, and observed a bunch of panics. Saw that the invalidation file was written. Restarted the server again and saw that it recovered itself by clearing the cache.
-
Benjamin Woodruff authored
This should help speed up builds that include test targets. `httpmock` was a bad fit for us because it has a really large dependency list that includes `async-std`. `mockito` appears to be much more popular. It depends on `hyper` and `tokio`, which we already pull in.
-
- 09 Jun, 2025 9 commits
-
-
vercel-release-bot authored
-
Sebastian "Sebbie" Silbermann authored
-
Luke Sandberg authored
Improve memory tracking in turbo-tasks-malloc ### What? Made the thread_local initializer `const` compatible. This skips per-thread lazy initialization of the threadlocal datastructure which allows us to skip a small amount of bootstrapping logic. Additionally, this allows us to access the native llvm implementation of threadlocals which can improve performance. See https://matklad.github.io/2020/10/03/fast-thread-locals-in-rust.html ### Performance Confusingly, the benchmarks are not positive, but vercel-site appears to be. Perhaps the 'small' benchmarks are just too small/ 
-
Vercel Release Bot authored
This auto-generated PR updates font data with latest available
-
Benjamin Woodruff authored
I noticed that we were depending on the old unmaintained `json` crate (https://lib.rs/crates/json). Update `tracing-chrome` to a newer version (https://github.com/thoren-d/tracing-chrome/releases) that uses `serde_json` instead.
-
Jiachi Liu authored
-
vercel-release-bot authored
-
Jiachi Liu authored
-
Donny/강동윤 authored
### What? Removes `benchmark-tiny` which _was_ stable at the time of introduction, but is not stable anymore. ### Why? It makes interpreting the performance difference harder
-