- 26 Oct, 2023 40 commits
-
-
vercel-release-bot authored
-
Jimmy Lai authored
-
Lee Robinson authored
- Fetch logging configuration is no longer experimental - Add `unstable_noStore` reference - Add `unstable_cache` reference - Add codemod docs for `next/og` import changes - Update docs around stable Server Actions - Add example of revalidating the entire data cache - Update static export docs for `next export` command removal - Update minimum required Node.js version - Add `viewport` and `generateViewport` reference Co-authored-by:
Balázs Orbán <18369201+balazsorban44@users.noreply.github.com> Co-authored-by:
Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
-
Michael Novotny authored
-
Michael Novotny authored
-
JJ Kasper authored
As discussed updates the warning with experimental config --------- Co-authored-by:Jimmy Lai <laijimmy0@gmail.com>
-
vercel-release-bot authored
-
Jimmy Lai authored
…7448)" This reverts commit 17bd232c. <!-- 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
-
Jimmy Lai authored
This reverts commit 6b18f397. <!-- 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
-
Tobias Koppers authored
* https://github.com/vercel/turbo/pull/6290 <!-- Tobias Koppers - fix hmr client to be actually reliable --> Closes WEB-1887 Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Sebastian Markbåge authored
We track dynamicUsageErr in patch-fetch usually and then abort the whole prerender if that happens. With PPR we use maybePostpone and not that so we should just not abort when we use ppr.
-
Zack Tanner authored
need to investigate this better --------- Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? client-only is allows in SSR, server-only should error Closes WEB-1883
-
Tobias Koppers authored
* https://github.com/vercel/turbo/pull/6289 <!-- Tobias Koppers - Revert "normalize pattern correctly to avoid slow path in matching" --> Closes WEB-1885
-
Andrew Clark authored
React upstream changes: - https://github.com/facebook/react/pull/27594 - https://github.com/facebook/react/pull/27584Co-authored-by:
Jiachi Liu <4800338+huozhi@users.noreply.github.com>
-
Jiachi Liu authored
Scope all `serverActions` config in one group "serverActions" to make it more semantics --------- Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Jiachi Liu authored
<img width="728" alt="image" src="https://github.com/vercel/next.js/assets/4800338/71f95a9d-3d9e-4191-ab85-6b88311d20c5"> --------- Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Zack Tanner authored
Rather than sending a warning, we should fail the build if a postpone call is caught. We should also fail the build if there are any errors during static generation similar to the non-ppr case. --------- Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Shu Ding authored
With Barrel Optimization, we are trying to "shortcut" the import to be directly pointing to the final target, as barrel files shouldn't have any side effects. However, there could be `"use client"` and `"use server"` directives which we can't ignore. Hence we must apply the `serverComponents` transform of SWC to these barrel files too. Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Justin Ridgewell authored
### What? Adds support for Server Actions imported by both server and client. ### Why? If an Action is imported by both the Client and RSC layers, we need to support them as if they're the same action. ### How? First, we need to ensure both layers create the same action hash ids, which we can then use to deduplicate actions imported by both layers. If a conflict is found, we prefer the RSC layer's action. Closes WEB-1879 --------- Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Shu Ding authored
There could be CSS files emitted in these chunks so both manifests need to filter them out. This fixes `app dir - css css support chunks should bundle css resources into chunks`.
-
vercel-release-bot authored
-
Leah authored
### Why? breaks hmr and causes some duplicate react instances (it was also supposed to fix some of those, seems neither version is correct) Closes WEB-1882
-
Houssein Djirdeh authored
Co-authored-by:Jiachi Liu <inbox@huozhi.im>
-
Tobias Koppers authored
add NEXT_HMR_TIMING env var to show hmr timings in turbopack Closes WEB-1880
-
Tobias Koppers authored
* https://github.com/vercel/turbo/pull/6268 <!-- Maia Teegarden - Update Turbopack Docs --> * https://github.com/vercel/turbo/pull/6278 <!-- Anthony Shew - Clearer Remote Cache upload spinner message. --> * https://github.com/vercel/turbo/pull/6288 <!-- Tobias Koppers - normalize pattern correctly to avoid slow path in matching --> Closes WEB-1877
-
Tobias Koppers authored
add the missing polyfill Closes WEB-1881
-
vercel-release-bot authored
-
Tobias Koppers authored
update manifest for daily test run Closes WEB-1876
-
Leah authored
### What? Given the structure: `/page.js` `/(group)/layout.js` Going to `/` would 404 Closes WEB-1878
-
Leah authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
vercel-release-bot authored
-
Jon Meyers authored
### What? [1] Use camelCase for SVG properties [2] Catch expected error in cookie functions ### Why? [1] Prints error to the console [2] If the cookies `set` or `delete` methods are called in a Server Component, an error is thrown ### How? [1] Change property names from kebab-case to camelCase [2] Catch error
-
Jimmy Lai authored
This PR enables the `experimental.webpackBuildWorker` to be on by default. This flag enables logic inside Next.js to run the compilation in an isolated worker. The reason for this is that the webpack compilation process retains a lot of memory for the whole duration of the build process because it uses some packages that leak. We don't need it for the rest of the process so it's best to use it in a worker and leave the memory to be used for static generation. This will improve memory usage during build, avoiding OOMs caused by webpack exceeding memory. <!-- 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:
JJ Kasper <jj@jjsweb.site>
-
Shu Ding authored
It should be `\.` here.
-
Justin Ridgewell authored
### What? Changes Server Actions to use a lazy `require()` statement instead of a lazy dynamic `import()`, to fix SA in the Edge runtime. ### Why? The Edge runtime has a restriction that it's not allowed to lazy load more files. The problem is that dynamic `import()` does exactly that, it defers importing those files until the call time. `require()` doesn't have this issue, because the chunks it would load are included instead of deferred. ### How? Just needed to modify the actions loader entry point… after hours of trying to get the action loader to evaluate in the node runtime and then import the actions in the edge runtime. Closes WEB-1874
-