- 24 Oct, 2024 26 commits
-
-
vercel-release-bot authored
-
Josh Story authored
Updates the heuristic to scoping prerender caches during dev. A cache scope will be created for every request if one does not already exist. If the request is a server action we create a new one. existing caches already expire after 30 seconds (unchanged) This updates the prefetch cache purge to be 5 seconds since so we don't mask short lifetime caches This also adds cache tracking to the first RSC render of the validation render. This means we now need to always do a second render regardless of whether there is a sync abort.
-
vercel-release-bot authored
-
Ismael authored
-
Sebastian "Sebbie" Silbermann authored
-
Jiwon Choi authored
Removed `"use cache"` directive on the before example of the code snippet.
-
Zack Tanner authored
This clears segment config errors that are corrected in development mode when using `dynamicIO`.
-
Zack Tanner authored
Follow-ups to #71812
-
vercel-release-bot authored
-
Rich Haines 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 # -->
-
Shu Ding authored
This PR simplifies our `flight-client-entry-plugin` to not re-compute the server reference IDs because they're already provided in `buildInfo` via our SWC transform. It's also a small performance win depending on the number of Server Actions in the project. Cherry-picked from #71463.
-
Jiachi Liu authored
-
Sebastian "Sebbie" Silbermann authored
-
Jiachi Liu authored
-
Tim Neutkens authored
Incorrectly mentions `(beta)`, it's been moved to stable in Next.js 15
👍 <!-- 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 # --> -
Jiachi Liu authored
-
Jiwon Choi authored
-
Donny/강동윤 authored
### What? Preserve the original import specifier when tree shaking, so the import analyzers after tree shaking can work. ### Why? This is required for `next/dynamic`. ### How? Closes PACK-3307
-
Josh Story authored
refines the error message for non-prerenderable holes while prerendering as well as the docs
-
vercel-release-bot authored
-
Jimmy Lai 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 # --> This changes the generated source map to not do the "webpack://next/dist/<file>" and instead use the relative path. this allows us to use the vanilla ignoreList "node_modules" config to also also ignore those files  
-
turbopack://[project]/...`file://...`Will Binns-Smith authored
This makes working with devtools more straightforward, reduces our own overhead when tracing stack frames in the error overlay, etc. Generated code from Turbopack or Next.js still use `turbopack://[turbopack]` or `turbopack://[next]` respectively. Test Plan: - [x] Update tests - [x] CI - [x] https://github.com/vercel/next.js/blob/475bdb1f743bf0b3552b40f85b615d87f4ae4904/test/development/app-dir/source-mapping/README.md --------- Co-authored-by:
Benjamin Woodruff <benjamin.woodruff@vercel.com> Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com>
-
Sebastian Markbåge authored
Turbopack doesn't recognize webpack:// and so errors otherwise. We don't need source maps for internals. <img width="774" alt="Screenshot 2024-10-23 at 10 13 02 PM" src="https://github.com/user-attachments/assets/72ec2ecc-7fbb-4a2a-9978-8d8c365ab966">
-
Jiachi Liu authored
### What When there's a replay console error showed up, display it in error overlay. #### Server Component Page <img width="480" alt="image" src="https://github.com/user-attachments/assets/7af65809-1e0e-4aa0-bffb-bc95a376fb02"> #### Server Component Page with Client Components <img width="480" alt="image" src="https://github.com/user-attachments/assets/1f8bd507-3e0f-43f3-9240-07c4aec16ab4"> --------- Co-authored-by:
Sebastian Markbage <sebastian@calyptus.eu>
-
Steven authored
This PR adds two experimental flags to configure sharpjs settings that may improve cpu for image optimization.
-
Jiachi Liu authored
-
- 23 Oct, 2024 14 commits
-
-
Vercel Release Bot authored
**breaking change for canary users: Bumps peer dependency of React from `19.0.0-rc-28668d39-20241023` to `19.0.0-rc-1631855f-20241023`** [diff facebook/react@28668d39...1631855f](https://github.com/facebook/react/compare/28668d39...1631855f) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/31340 </details>
-
vercel-release-bot authored
-
Sam Ko authored
## Why? The `turbo` config is still experimental in v15. - Fixes https://github.com/vercel/next.js/issues/71750 - Related PR: https://github.com/vercel/next.js/pull/71755
-
Jiachi Liu authored
-
Sebastian Markbåge authored
This lets us show Server Components (and Host Components) in the Parent Stack passed to errors. <img width="1039" alt="Screenshot 2024-10-23 at 12 51 10 PM" src="https://github.com/user-attachments/assets/5912e750-b544-403d-8d5a-bce91c01b3a8">
-
Josh Story authored
We ended up with up to three prerender passes as we added support for new use cases like lazy module initializaiton. This update refactors the PPR pathway to have at most two renders. I will follow up with a refactor of the non-ppr pathway next.
-
Jiachi Liu authored
-
JJ Kasper authored
-
Maia Teegarden authored
### What? Fixes code examples for configuring Turbopack. Turbopack Dev is stable, but we're keeping the configuration options under `experimental` until Turbopack Build is stable as well. Most of these options will not change, but we didn't want a combination of experimental and stable options. Closes PACK-3324
-
vercel-release-bot authored
-
Hendrik Liebau authored
Similar to how #71669 fixed a race condition when setting the manifests singleton regarding the server action manifests, this PR fixes the same race condition for the client reference manifests.
-
Josh Story authored
-
Vercel Release Bot authored
-
Zack Tanner authored
`easy` and `just` are failing lint checks.
-