- 30 Jul, 2025 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Backports: - #82118 --------- Co-authored-by:Steven <steven@ceriously.com>
-
- 29 Jul, 2025 1 commit
-
-
Zack Tanner authored
Backports: - #82114 Co-authored-by:Steven <steven@ceriously.com>
-
- 12 Jun, 2025 1 commit
-
-
vercel-release-bot authored
-
- 11 Jun, 2025 1 commit
-
-
Zack Tanner authored
Backports: - #76880 - #77044 - #77053 - #77395 - #77414
-
- 20 May, 2025 2 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
This backports https://github.com/vercel/next.js/pull/79386 to 14 release channel
-
- 08 Apr, 2025 2 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
The previous [backport](https://github.com/vercel/next.js/pull/77794) caused an issue due to how imports are resolved on canary vs v14, resulting in a message about using node.js APIs in middleware. This moves the import to the `web` directory and adds a test case for the warning. Closes NDX-1014
-
- 07 Apr, 2025 1 commit
-
-
vercel-release-bot authored
-
- 04 Apr, 2025 1 commit
-
-
Zack Tanner authored
Backports: - #64923
-
- 24 Mar, 2025 2 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
Backports https://github.com/vercel/next.js/pull/77474 to v14
-
- 17 Mar, 2025 2 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
Backports https://github.com/vercel/next.js/pull/77201 to v14 release branch
-
- 11 Feb, 2025 1 commit
-
-
vercel-release-bot authored
-
- 10 Feb, 2025 4 commits
-
-
Zack Tanner authored
-
Zack Tanner authored
Backports: - #75766
-
Zack Tanner authored
Backports: - #75561 - #73482 --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Jiachi Liu authored
-
- 07 Jan, 2025 3 commits
-
-
vercel-release-bot authored
-
Janka Uryga authored
Fixes #74062 (`jotai` ran into this error [when they added `"type": "commonjs"` to their package.json](https://github.com/pmndrs/jotai/discussions/2579#discussioncomment-9812492)) > this is a bug in the transform we do when a `'use client'` directive is encountered. I think what's happening is that we're creating a virtual file that uses ESM import/export syntax, but it's called proxy.js (not proxy.mjs), so the `"type": "commonjs" `makes turbopack "correctly" upset at the ESM syntax. https://github.com/vercel/next.js/issues/74062#issuecomment-2555922867 The (slightly kludgy) solution is to use `proxy.mjs` or `proxy.cjs` to force the module format, bypassing the issue where `proxy.js` changes meaning depending on `package.json#type`.
-
JJ Kasper authored
This backports https://github.com/vercel/next.js/pull/74164 to leverage built-in waitUntil if available instead of using the approach that keeps the stream open until the waitUntil promise resolves. x-ref: [slack thread](https://vercel.slack.com/archives/C02K2HCH5V4/p1736211642221149?thread_ts=1734707275.666089&cid=C02K2HCH5V4)
-
- 03 Jan, 2025 1 commit
-
-
Steven authored
Backports PR https://github.com/vercel/next.js/pull/74257 to 14.x
-
- 26 Dec, 2024 1 commit
-
-
vercel-release-bot authored
-
- 24 Dec, 2024 2 commits
-
-
Zack Tanner authored
Backports: - #71564 - #74154 --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Zack Tanner authored
Backports: - #73900 Co-authored-by:Hendrik Liebau <mail@hendrik-liebau.de>
-
- 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 1 commit
-
-
vercel-release-bot authored
-