- 19 Dec, 2024 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Updates React from 14898b6a9 to 178c267a4e. ### React upstream changes - https://github.com/facebook/react/pull/31842 - https://github.com/facebook/react/pull/31841
-
- 13 Dec, 2024 2 commits
-
-
Steven authored
Backport https://github.com/vercel/next.js/pull/73925 to 14.x
-
Steven authored
Backport https://github.com/vercel/next.js/pull/73923 to 14.x
-
- 12 Dec, 2024 1 commit
-
-
Hendrik Liebau authored
> [!NOTE] > This is a backport of #73732 for Next.js 14. When using dependencies in Middleware that make use of dynamic code evaluation, Next.js emits a build error because this is not supported in the Edge runtime. In rare cases, when the code can not be reached at runtime and can't be removed by tree-shaking, users might opt in to using the `unstable_allowDynamic` config. When combined with pnpm, the provided glob patterns as documented at https://nextjs.org/docs/messages/edge-dynamic-code-evaluation#possible-ways-to-fix-it did not match correctly because of pnpm's use of the `.pnpm` directory. To fix the pattern matching, we need to provide the `dot` option to [picomatch](https://github.com/micromatch/picomatch), which enables dotfile matching. _Side note: Ideally we would detect dynamic code evaluation after tree shaking, to reduce the number of cases where users need to revert to using `unstable_allowDynamic`._ fixes #51401
-
- 11 Dec, 2024 1 commit
-
-
Hendrik Liebau authored
- installs React v18 instead of latest in tests - removes Next.js v15 references from lockfile - installs "current" native SWC binaries instead of latest
-
- 04 Dec, 2024 2 commits
-
-
vercel-release-bot authored
-
Wyatt Johnson 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 is a backport of https://github.com/vercel/next.js/pull/73274 which resolves a bug with response cloning.
-
- 03 Dec, 2024 1 commit
-
-
vercel-release-bot authored
-
- 02 Dec, 2024 2 commits
-
-
JJ Kasper authored
x-ref: https://github.com/vercel/next.js/pull/73125
-
Zack Tanner authored
Backports: - https://github.com/vercel/next.js/pull/70997 - https://github.com/vercel/next.js/pull/73138 To avoid introducing the larger worker refactor in #68546, this PR introduces additional handling needed to special case the "restarting" flow to not exit the parent process.
-
- 25 Nov, 2024 1 commit
-
-
JJ Kasper authored
-
- 13 Nov, 2024 2 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
Backports: https://github.com/vercel/next.js/pull/68683Co-authored-by:
Develliot <elliotrevan@gmail.com>
-
- 07 Nov, 2024 1 commit
-
-
Jiachi Liu authored
-
- 05 Nov, 2024 5 commits
-
-
vercel-release-bot authored
-
Jiachi Liu authored
backport #71723
-
JJ Kasper authored
When `pages/500` uses `getStaticProps` we can honor statically generating the page but we can't send a `Cache-Control` with `stale-while-revalidate` as we shouldn't be caching errored pages ever. This ensures we handle that case and add a regression test for it. <!-- 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
### What Backport #65102, #65343 (as they are fixing the same issue) x-ref: [slack](https://vercel.slack.com/archives/C0676QZBWKS/p1730402565599979?thread_ts=1729588414.805619&cid=C0676QZBWKS) --------- Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
JJ Kasper 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 # -->
-
- 30 Oct, 2024 1 commit
-
-
JJ Kasper authored
This ensures we publish under separate tag for v14 backports.
-
- 23 Oct, 2024 1 commit
-
-
vercel-release-bot authored
-
- 10 Oct, 2024 1 commit
-
-
JJ Kasper authored
Follow-up to https://github.com/vercel/next.js/pull/70649 this tweaks the backport to properly clone and return original response so that pending revalidates aren't sharing an already used response.
-
- 08 Oct, 2024 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Backports: - #70761 Co-authored-by:Wyatt Johnson <accounts+github@wyattjoh.ca>
-
- 06 Oct, 2024 1 commit
-
-
Steven authored
- Backport https://github.com/vercel/next.js/pull/70608 to `14.2.x` Co-authored-by:
Joseph <sephxd1234@gmail.com>
-
- 05 Oct, 2024 1 commit
-
-
Steven authored
- Backport https://github.com/vercel/next.js/pull/70730 to `14.2.x`
-
- 04 Oct, 2024 5 commits
-
-
Steven authored
-
Steven authored
-
Steven authored
- Backport https://github.com/vercel/next.js/pull/70529 to `14.2.x`
-
Zack Tanner authored
Backports: - #65063 - #65233 --------- Co-authored-by:Andrew Gadzik <andrew.gadzik@vercel.com>
-
Jiachi Liu authored
-
- 01 Oct, 2024 5 commits
-
-
Steven authored
- Backport https://github.com/vercel/next.js/pull/70298 to `14.2.x`
-
vercel-release-bot authored
-
JJ Kasper authored
This fixes a race where if the body was resolved before the clone operation, it would clone later, resulting in an error being thrown due to the body already being consumed. backports #70082 --------- Co-authored-by:Wyatt Johnson <accounts+github@wyattjoh.ca>
-
Jiachi Liu authored
backport #70508 Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Jiachi Liu authored
backport #70330 Fixes #69912 --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
- 30 Sep, 2024 3 commits
-
-
JJ Kasper authored
This backports #70446 to 14-2-1 Fixes #70403 ### What? When `revalidateTag()` is called directly in server components, the cache is not purged for the corresponding tags. Reproduction steps available in #70403 ### How? Check [app-render.tsx](https://github.com/vercel/next.js/compare/canary...abhi12299:fix-revalidatetag-rsc?expand=1#diff-a3e2e024db1faa1b501e0dd6040eaaf0d931cb9878ae0fb0f4c3658daa982768) This issue was introduced in #65296 in this file: [revalidate.ts](https://github.com/vercel/next.js/pull/65296/files#diff-7f0cb5bb30d44b9153d724e31c25859b9aab6cc258b35563a1d9464cd0688283). The lines removed from the file resulted in the revalidation checks to be skipped when there is an RSC request. Also fixed checks on `pendingRevalidates` to also check for `revalidatedTags`. Co-authored-by:
Abhishek Mehandiratta <36722596+abhi12299@users.noreply.github.com>
-
JJ Kasper authored
-
JJ Kasper authored
-