- 10 Nov, 2023 9 commits
-
-
vercel-release-bot authored
-
YOSHIDA Junki authored
Removed router.events example from the document because it does not exist. URL: https://nextjs.org/docs/pages/api-reference/functions/use-router#routerevents <!-- 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 # --> Co-authored-by:
Lee Robinson <me@leerob.io>
-
Karl Horky 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 # --> ### What? Avoid copying request headers to response ### Why? Copying request headers to response allows for reflection attacks https://github.com/vercel/next.js/issues/57410 ### How? Remove the `headers:` property assignment cc @leerob Followup to https://github.com/vercel/next.js/pull/58300 Fixes #57410
-
Lee Robinson authored
-
Leah authored
### What? We previously marked `/src/middleware` as a missing page Fixes #42921 Closes PACK-1926 --------- Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Tim Neutkens authored
Ensures the CSP header is still set on the response.
-
Tim Neutkens authored
Removes the passing of headers for the response.
-
vercel-release-bot authored
-
Josh Story authored
Updates React from 746890329 to 0e352ea01. - https://github.com/facebook/react/pull/27684 - https://github.com/facebook/react/pull/27665 - https://github.com/facebook/react/pull/27671 - https://github.com/facebook/react/pull/27680
-
- 09 Nov, 2023 18 commits
-
-
vercel-release-bot authored
-
Leah authored
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Dennis Wilm authored
Corrected a link that linked to the wrong page. <!-- 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 # -->
-
Tobias Koppers authored
### What? gives all elements in the array unique keys should fix #57709 and fix #57743
-
Arseny authored
### What? This pull request integrates the exemplary setup for a self-hosted Next.js application utilizing Redis as a shared cache storage. The solution supports caching at both the App and Pages routers in default and standalone modes, as well as partial pre-rendering, facilitated by the [`@neshca/cache-handler`](https://github.com/caching-tools/next-shared-cache/tree/canary/packages/cache-handler) package. The package enables customizing cache handlers and replacing the default cache provided by Next.js seamlessly. ### Why? The motivation behind this pull request is to provide an example demonstrating how Redis can be used as a shared cache in a self-hosted environment, thereby improving the scalability of hosting multiple instances of a Next.js application.
-
Lee Robinson authored
[This page](https://nextjs.org/docs/app/building-your-application/optimizing/analytics) was not yet mentioning `useReportWebVitals`. Closes https://github.com/vercel/next.js/issues/57715.
-
Jimmy Lai authored
This PR fixes a bug where parallel routes would not apply appropriately on navigation when used within slots. The following scenarios: ``` /foo /bar /@slot /[...catchAll] ``` or ``` /foo /[...catchAll] /@slot /bar ``` will now function correctly when accessing /foo/bar, and Next.js will render both /bar and the catchall slots. The issue was that the tree constructed by `next-app-loader` for a given path, /foo/bar in the example, would not include the paths for the catch-all files at build time. The routing was done 1-1 when compiling files, where a path would only match one file, with parallel routes, a path could hit a defined path but also a catch all route at the same time in a different slot. The fix consists of adding another normalisation layer that will look for all catch-all in `appPaths` and iterate over the other paths and add the relevant information when needed. The tricky part was making sure that we only included the relevant paths to the loader: we don't want to overwrite a slot with a catch all if there's already a more specific subpath in that slot, i.e. if there's /foo/@slot/bar/page.js, no need to inject /foo/@slot/bar/[...catchAll]. One thing that is not supported right now is optional catch all routes, will add later. fixes #48719 fixes #49662 -
vercel-release-bot authored
-
Tobias Koppers authored
* https://github.com/vercel/turbo/pull/6399 * https://github.com/vercel/turbo/pull/6393 * https://github.com/vercel/turbo/pull/6403 * https://github.com/vercel/turbo/pull/6404 * https://github.com/vercel/turbo/pull/6394 * https://github.com/vercel/turbo/pull/6405 * https://github.com/vercel/turbo/pull/6351
-
OJ Kwon authored
### What Apply correct url rewrite behavior in the specific context (pages/api). This won't change anything yet, but it will prevent breaking changes when turbopack makes future changes.
-
Rich Haines authored
This PR fixes the terminal link to server actions size limitations for body size limit. The link is wrong and sending people to a 404
-
vercel-release-bot authored
-
Josh Story authored
Updated React from 7508dcd5c to 746890329. - https://github.com/facebook/react/pull/27674
-
Zack Tanner authored
Wraps this test in a `check` since the experimental log seems to occasionally come in late ([x-ref](https://github.com/vercel/next.js/actions/runs/6805954994/job/18506429726#step:27:410))
-
Sebastian Markbåge authored
This phrasing was changed.
-
Zack Tanner authored
Instead of requiring React in `maybePostpone` (which is susceptible to referencing the wrong version of React during build time, such as in the case where the static worker patches fetch within an app-route, which doesn't have an experimental runtime), this provides the postpone API to the `staticGenerationStore`. That way we know the API is available in render which is when we'd expect to postpone.
-
- 08 Nov, 2023 13 commits
-
-
vercel-release-bot authored
-
Sebastian Markbåge authored
The "postpone" terminology is internal to React and can be used for more things than just this. It's also a mechanism we may or may not rely on. --------- Co-authored-by:Zack Tanner <zacktanner@gmail.com>
-
Sebastian Markbåge authored
Other ways such as on the client.
-
Zack Tanner authored
Fixes a broken link, shortens the title, and adds another possible way to resolve the error. Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
vercel-release-bot authored
-
Josh Story authored
Updated React from 2983249dd to 7508dcd5c. - https://github.com/facebook/react/pull/27672 - https://github.com/facebook/react/pull/27132 - https://github.com/facebook/react/pull/27646 - https://github.com/facebook/react/pull/26446
-
Jimmy Lai authored
This PR fixes the bug in which interception routes of the form `(.)[param]` would not intercept navigations. The bug happened because we would not create a dynamic route matcher for the intercepted route, so we would never match the correct dynamic route when hitting the server, falling back to the base one. The fix consists of fixing the logic that checks for a dynamic route so that it checks the correct path when handling an interception route. There's probably a better fix here, advice welcome fixes #52533
-
Maia Teegarden authored
-
Zack Tanner authored
Follow up to #58203 to skip this in tests to avoid issues once we cut stable
-
Michael Novotny authored
### Description Adds config for experimental PPR support ### Related Issue(s)/Incident Prior art: #57444 ### Best Way to Test Visit → docs/app/api-reference/next-config-js/partial-prerendering Co-authored-by:
Amy Burns <5012825+timeyoutakeit@users.noreply.github.com> Co-authored-by:
Lee Robinson <9113740+leerob@users.noreply.github.com>
-
-
vercel-release-bot authored
-
Zack Tanner authored
Fixes a bug where when `config.experimental.ppr` was set, we didn't show the proper warning indicator that the feature is experimental.
-