- 10 Apr, 2025 25 commits
-
-
vercel-release-bot authored
-
Vercel Release Bot authored
-
Tobias Koppers authored
### What? Quick debug check to panic for duplicate modules
-
Wyatt Johnson authored
When rendering the page on Vercel, we send the `x-matched-path` header to indicate which route should be rendered. Sometimes, like in the case of a middleware rewrite, we will rewrite a path to a statically generated one. This results in a `x-matched-path` header being equal to the generated page and not the route with the dynamic path params in it. This ensures that if we get such a path that we match against that we do save the result of the path matching as they are valid parameters. This also fixes a related bug associated with route denormalization which must occur before the routes i18n is parsed. <!-- 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 # --> Fixes #77789 --------- Co-authored-by:
Jiwon Choi <devjiwonchoi@gmail.com>
-
Delba de Oliveira authored
Updating the docs after playing around with `useLinkStatus`: https://github.com/vercel/next-app-router-playground/pull/184 Closes: https://linear.app/vercel/issue/DOC-4514/update-docs Main changes: - Update introduction - Simplify example - Add example for gracefully handling fast navigations (avoiding UI flash)
-
Delba de Oliveira authored
Decoupling from: https://github.com/vercel/next.js/pull/73437 - Add "How `use cache` works" section - Clarify cache keys inputs - Describe what happens during build, runtime, and revalidation - Correct the default values for the `cacheLife` profiles - Add the default time for `expireTime` - Add note about `staleTimes` and `expireTime` affecting the default cache profile
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
vercel-release-bot authored
-
Sebastian "Sebbie" Silbermann authored
-
Donny/강동윤 authored
### What? Fix turbopack es analyzer, for the case below ```js const shouldRun = () => false; export default function run() { if (shouldRun()) { var x = true; } if (x) { return 'should not run'; } return 'should run'; } ``` ### Why? ### How? Fixes #77126 Closes PACK-4159 -
Niklas Mischkulnig authored
This is absolutely useless with numerical ids (prod build with `turbopackMinify: false`): ```css /* 51318 */ .base2-module__zzC_ua__base { color: #ff0200; } /* 29244 */ .base2-scss-module-scss-module__JjfRsa__base { color: #ff0300; } /* 85234 */ .base-module__DNnTeq__base { color: red; } /* 29244 */ .base2-scss-module-scss-module__JjfRsa__base { color: #ff0300; } ``` -
Sebastian "Sebbie" Silbermann authored
-
Delba de Oliveira authored
Closes: https://linear.app/vercel/issue/DOC-4469/turbopack-for-builds --------- Co-authored-by:
Sebastian "Sebbie" Silbermann <sebastian.silbermann@vercel.com>
-
Tobias Koppers authored
<!-- 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 # -->
-
Sebastian "Sebbie" Silbermann authored
Also inlined some of the indirections that we no longer need.
-
Kolja authored
Co-authored-by:Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
-
Sebastian "Sebbie" Silbermann authored
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing Turbopack.
-
Vercel Release Bot authored
This auto-generated PR updates the production integration test manifest used when testing Turbopack.
-
Niklas Mischkulnig authored
Previously, if `require("./dynamic-files/"+name)` had only a single match, it would always return that one, regardless of whether `name` was equal to the matches' filename or not. Closes https://github.com/vercel/next.js/issues/74664 Closes PACK-4309 -
Will Binns-Smith authored
sourcecode -> source code sourcemap -> source map
-
Niklas Mischkulnig authored
-
Tobias Koppers authored
Turbopack: fix a bug where marking a task a completed causes a panic when reading the output (#77922) ### What? When using mark_finished() on a task, reading that task while it's still in progress will lead to a panic because it would try to schedule that task for recomputation, but it's already scheduled.
-
- 09 Apr, 2025 15 commits
-
-
マルコメ authored
## Description At #76583, tailwind theme font referenced the [Geist font](https://vercel.com/font). ```css // globals.css @import "tailwindcss"; ~~~ @theme inline { --color-background: var(--background); --color-foreground: var(--foreground); --font-sans: var(--font-geist-sans); --font-mono: var(--font-geist-mono); } ~~~ ``` However, these `font-sans` and `font-mono` variables aren't used now. This PR uses them instead of `font-[family-name:var(--font-geist-sans)]` and `font-[family-name:var(--font-geist-mono)]` for convinience. CC: @samcx Co-authored-by:
Sam Ko <sam@vercel.com>
-
Jiachi Liu authored
-
Jiachi Liu authored
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? Use the correct env var Regression from #77894
-
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
🙈
-