- 15 Aug, 2023 3 commits
-
-
vercel-release-bot authored
-
vercel-release-bot authored
-
JJ Kasper authored
removes usage of turbo and uses the default node version inside the image.
-
- 14 Aug, 2023 28 commits
-
-
Shu Ding authored
This PR changes the internal `createActionProxy` util from a default export to a named export, as the default export could be problematic if it's built without the "esModuleInterop" step. --------- Co-authored-by:Balázs Orbán <info@balazsorban.com>
-
OJ Kwon 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? PR dumps out next-swc's glibc linkage after build completes, for easier bisect if regression occurs.
-
vercel-release-bot authored
-
Jiachi Liu authored
x-ref: https://github.com/vercel/next.js/pull/51647 follow up for the code indexing issue for "build/**" folder, previous solution seem not working, trying just "build/**" without prefix
-
JJ Kasper authored
This rolls back our build image for our swc builds as it seems to cause a GLIBC version conflict. x-ref: [slack thread](https://vercel.slack.com/archives/C04KC8A53T7/p1692049361819349?thread_ts=1692039503.188119&cid=C04KC8A53T7)
-
Will Binns-Smith authored
This regressed in vercel/turbo#5661 when `context` was renamed `file_path`.
-
Tibor Sándor authored
This commit fixes a typo in the `<head> output` (twitter-image.alt.txt) code block
-
OJ Kwon authored
### What Pairing PR to https://github.com/vercel/turbo/pull/5714, which I believe last piece to reenable correct datadog test reports for daily next.js integration + turbopack. 1. Creates a unique suite name to avoid collision / merging across different env / grouped test run 2. revert suitename template (which is for _suites_, not _suite_ for top level) as 1 resolves uniqueness
-
Kyle McDonald authored
When implementing `opengraph-image` in my [personal-site-project](https://github.com/kylemcd/personal-site). I was consistently running into issues where custom fonts would either only work locally or only work on vercel. To me it seemed like differences in pathing in `edge` vs `nodejs` runtimes. After digging around I found issue #48081, more specifically [this comment](https://github.com/vercel/next.js/issues/48081#issuecomment-1565842740) where moving the `fetch` for the font into the `Image` function solved the issue. I'm not sure if this is 100% the correct fix, or if this is an issue that needs to be solved in another way. If that's not the case this PR updates the documentation around `opengraph-image` to have the fetch for custom fonts inside of the `Image` function.
-
Dima Voytenko authored
An experimental test mode that enables integration tests to mock server-side fetch requests in Playwright tests. For explanation on how this works, see the [`next-playwright/README.md`](https://github.com/vercel/next.js/pull/52520/files#diff-3b8da7782c16f015df5afafe0ac11247f5b8e5a1c0dbede341ca2b5124dfd924).
-
Lacy Morrow authored
### What? Update Tanstack query URL ### Why? The latest Tanstack query version is v4, the docs currently list v3
-
Jiachi Liu authored
Add script of generating release log. To access the changelog just run the below script (copy content with `pbcopy` on MacOS) ```js node ./scripts/generate-release-log.mjs | pbcopy ```
-
Zack Tanner authored
This adds a test case for ipv6 hostnames in standalone mode - Follow up to https://github.com/vercel/next.js/pull/53131
-
JJ Kasper authored
All have docker available now so don't need this label to distinguish anymore.
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Jiachi Liu authored
ensure `next` is the dependency of third-parties package so turbo will build next first then `@next/third-parties` to avoid type failing --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Rishabh Poddar authored
Co-authored-by:Lee Robinson <me@leerob.io>
-
Aryan Malik authored
Added a switcher on a code snippet under heading -> `Using Cookies`, just like the other code snippets on this page got one.. (For those who don't know what a switcher is -> It's just a simple functionality for changing `typescript` code to `javascript` and vice-versa, kind of a UI feature for better experience` Co-authored-by:Balázs Orbán <18369201+balazsorban44@users.noreply.github.com>
-
Jiachi Liu authored
x-ref: https://github.com/vercel/next.js/actions/runs/5854800073/job/15871731468 Do not use the `packages/next` tsconfig, aligning tsconfig with other `@next/` packages. So it won't run tsc with `tsec` plugin
-
Tim authored
Co-authored-by:
Kevintjuhz <kevin@kqcreations.com> Co-authored-by:
Kevintjuhz <k.quaedvlieg@outlook.com> Co-authored-by:
Lee Robinson <me@leerob.io>
-
vercel-release-bot authored
-
Tim Neutkens authored
Noticed a small typo, this fixed 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 # -->
-
vercel-release-bot authored
-
Ngô Đức Anh authored
### What? This PR makes it easier to use Next.js with IPv6 hostnames such as `::1` and `::`. ### How? It does so by removing rewrites from `localhost` to `127.0.0.1` introduced in #52492. It also fixes the issue where Next.js tries to fetch something like `http://::1:3000` when `--hostname` is `::1` as it is not a valid URL (browsers' `URL` class throws an error when constructed with such hosts). It also fixes `NextURL` so that it doesn't accept `http://::1:3000` but refuse `http://[::1]:3000`. It also changes `next/src/server/lib/setup-server-worker.ts` so that it uses the server's `address` method to retrieve the host instead of our provided `opts.hostname`, ensuring that no matter what `opts.hostname` is we will always get the correct one. ### Note I've verified that `next dev`, `next start` and `node .next/standalone/server.js` work with IPv6 hostnames (such as `::` and `::1`), IPv4 hostnames (such as `127.0.0.1`, `0.0.0.0`) and `localhost` - and with any of these hostnames fetching to `localhost` also works. Server Actions and middleware have no problems as well. This also removes `.next/standalone/server.js`'s logging as we now use `start-server`'s logging to avoid duplicates. `start-server`'s logging has also been updated to report the actual hostname.   The above pictures also demonstrate using Server Actions with Next.js after this PR.  Fixes #53171 Fixes #49578 Closes NEXT-1510 Co-authored-by:
Tim Neutkens <6324199+timneutkens@users.noreply.github.com> Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
vercel-release-bot authored
-
JJ Kasper authored
This ensures env variables are passed through as expected when building the next-swc binaries, also removes an extra GH actions that isn't really needed as it's just a wrapper around `docker run`. Validated changes against run here https://github.com/vercel/next.js/actions/runs/5851719808/job/15862899331
-
JJ Kasper authored
This fixes unexpected cache hits occurring causing latest next-swc changes to not be built for the docker based builds. Noticed in our turbo run summaries for these builds that no input files were detected most likely due to older Node.js/pnpm versions being used from the old Docker image. This also updates to leverage new runner labels for better build perf cutting build times down from over an hour down to around 20 min. Fixes build issue on aarch64-linux-musl due to `TurboMalloc` not being able to resolve. Test build done here https://github.com/vercel/next.js/actions/runs/5850893681/job/15860929304 x-ref: https://github.com/vercel/next.js/actions/runs/5843580924/job/15845848384 x-ref: https://github.com/vercel/next.js/actions/runs/5837652747/job/15833506858 x-ref: https://github.com/vercel/next.js/actions/runs/5837652747/job/15833506925 x-ref: https://github.com/vercel/next.js/actions/runs/5837652747/job/15833507067 x-ref: https://github.com/vercel/next.js/actions/runs/5837652747/job/15833507135
-
- 12 Aug, 2023 6 commits
-
-
vercel-release-bot authored
-
Hüsrev authored
-
Zack Tanner authored
`expect` is an unsupported header for undici: https://github.com/nodejs/undici/blob/c83b084879fa0bb8e0469d31ec61428ac68160d5/lib/core/request.js#L354 -- this filters it out so that the API routes don't throw an internal server error if that header is included. Also added a test case for the previously submitted PR that was added for `content-length: 0` - x-ref: #53843 Fixes #53822 (erroneously closed by a content-length issue being fixed)
-
Josh Story authored
Updated React from cb3404a0c to f359f9b41. ### React upstream changes - https://github.com/facebook/react/pull/27191 - https://github.com/facebook/react/pull/27209 - https://github.com/facebook/react/pull/27199 - https://github.com/facebook/react/pull/27218 - https://github.com/facebook/react/pull/27217 - https://github.com/facebook/react/pull/27212
-
Jiachi Liu authored
### What? We change the not-found rendering strategy to the origin one which recovers the not found error from the flight data, and hit the error boundary to display the closet not found component. For parallel `@slot` we shouldn't pass down the not-found boundary, the boundary is only for `@children`. ### Why? We're having a lot of not-found matching issues that manually searching for not found and layout won't be accurate as we have various scenarios like `(group)` routes, dynamic routes, etc. ### How? Only render html with empty body so that the error can recover from flight and render the proper not-found component during hydration. One change for metadata is that we need to get the "not-found" metadata in the initial render, so we'll catch the not-found error once there first and start render the "not-found" metadata and put it in the flight data. Then when it recovers it's still preserved. Fixes #53694
-
Kevin Pham authored
Previous of after (before in linked issue) ``` ❯ pnpm add --save-dev @next/eslint-plugin-next Already up to date Progress: resolved 525, reused 517, downloaded 0, added 0, done Done in 6.4s ``` Resolves #53937
-
- 11 Aug, 2023 3 commits
-
-
Artur Bień authored
Adds support for base64-encoded `placeholder`. Enables using placeholders without the "blur" effect. Fixes #47639 - [x] Add support for DataURL placeholder - [x] Add tests - [x] Update docs Co-authored-by:Steven <229881+styfle@users.noreply.github.com>
-
Dima Voytenko authored
-
Donny/강동윤 authored
### What? Update swc crates to https://github.com/swc-project/swc/commit/54f38cb47e4978b96f422c2ca2e7da1c7ae9283f ### Why? To apply minifier bugfixes. ### How? Closes WEB-1358 Fixes #53723 --- turbopack counterpart: https://github.com/vercel/turbo/pull/5699
-