- 10 Apr, 2024 12 commits
-
-
vercel-release-bot authored
-
Jeongjin Oh 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 ### 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 --> fixes #63803 ## What I do? - If the loader file export the function as `named`, Next.js throws the error. - But this error is a bit confusing for the developers. - So I open this PR for showing the accurate error message. ## AS-IS / TO-BE ### AS-IS ``` TypeError: Cannot use 'in' operator to search for '__next_img_default' in undefined ``` <img width="1202" alt="스크린샷 2024-03-28 16 10 53" src="https://github.com/vercel/next.js/assets/33178048/e7c81cb5-7976-46ff-b86f-9c8fd9a7a681"> ### TO-BE ``` Error: The loader file must export a default function that returns a string. See more info here: https://nextjs.org/docs/messages/invalid-images-config ``` <img width="500" alt="스크린샷 2024-03-28 16 10 53" src="https://github.com/vercel/next.js/assets/33178048/c391e61b-6a44-4f85-8600-28ab6cb5b0eb"> --------- Co-authored-by:
Steven <steven@ceriously.com>
-
Tobias Koppers authored
### What? align integration tests with e2e test command-wise ### Why? ### How? Closes PACK-2929 --------- Co-authored-by:Balázs Orbán <info@balazsorban.com>
-
Jiachi Liu authored
Follow up for #64294 to make turbopack side work as well --------- Co-authored-by:Tobias Koppers <tobias.koppers@googlemail.com>
-
Tim Neutkens authored
## What? Updates the loader documentation to the format. <!-- 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 # --> Closes NEXT-3061
-
Jiachi Liu authored
### What CSS imports in components that loaded by `next/dynamic` in client components will cause the css are missing initial in SSR, and loaded later on client side which will lead to FOUC. This PR fixes the issue and get CSS preloaded in the SSR for dynamic components. ### Why The CSS from client components that created through `next/dynamic` are not collected in the SSR, unlike RSC rendering we already collect the CSS resources for each entry so we included them in the server rendering so the styles are availble at that time. But for client components, we didn't traverse all the client components and collect the CSS resources. In pages router we kinda collect all the dynamic imports and preload them during SSR, but this approach is not able to be applied to app router due to different architecture. Since we already have all the dynamic imports info and their related chunks in react-loadable-manifest, so we can do the similar "preloading" thing in app router. We use the current dynamic module key (`app/page.js -> ../components/foo.js`) which created by SWC transform and match it in the react loadable manifest that accessed from `AsyncLocalStorage`, to get the css files created by webpack then render them as preload styleshee links. In this way we can SSR all the related CSS resources for dynamic client components. The reason we pass down the react loadable manifest through `AsyncLocalStorage` is that it's sort of exclude the manifest from RSC payload as it's not required for hydration, but only required for SSR. Note: this issue only occurred in dynamic rendering case for client components. ### Other Changes Overview - Change the react loadable manifest key from pages dir based relative path to a source dir based relative path, to support cases with both directory or only one of them Closes NEXT-2578 Fixes #61212 Fixes #61111 Fixes #62940 Replacement for #64021 but only with production test
-
Tim Neutkens authored
## What? Updates the manifest with the `test/integration` run. <!-- 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 # --> Closes NEXT-3058
-
Vercel Release Bot authored
This auto-generated PR updates font data with latest available
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing Turbopack.
-
Tim Neutkens authored
## What? Currently any configuration issue like including `.babelrc` was not highlighted during Turbopack build. This PR solves that issue as well as ensuring the warnings are not double-logged because of a change that was supposed to be development-only. <!-- 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 # --> Closes NEXT-3049
-
Martin Goutry authored
This fixes a wrong route in the [staleTimes](https://nextjs.org/docs/app/api-reference/next-config-js/staleTimes) doc Co-authored-by:
Sam Ko <sam@vercel.com>
-
Ahsan Moin authored
`functionaility` -> `functionality` `programatically` -> `programmatically` `recored` -> `record` `specfy` -> `specify` <!-- 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 # -->
-
- 09 Apr, 2024 14 commits
-
-
vercel-release-bot authored
-
Tobias Koppers authored
* https://github.com/vercel/turbo/pull/7912 <!-- Tobias Koppers - fix edge condition in environment --> * https://github.com/vercel/turbo/pull/7914 <!-- hrmny - feat: support interop for namespace importing cjs function exports -->
-
Sam Ko authored
## Why? Forgot to add this change in here → https://github.com/vercel/next.js/pull/64264. Closes NEXT-3055
-
Sam Ko authored
## Why? This fixes the ordering of `--experimental-debug-memory-usage` so the help output for experimental options are alphabetical/ordered properly (grouped at the end). - Related https://github.com/vercel/next.js/pull/63869 Closes NEXT-3054
-
Zack Tanner authored
Provides a `revalidateReason` argument to `getStaticProps` ("stale" | "on-demand" | "build"). - Build indicates it was run at build time - On-demand indicates it was run as a side effect of [on-demand revalidation](https://nextjs.org/docs/pages/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation) - Stale indicates the resource was considered stale (either due to being in dev mode, or an expired revalidate period) This will allow changing behavior based on the context in which it's called. Closes NEXT-1900 -
Sam Ko authored
## Why? When we fetch the same cache key (URL) but add an additional tag, the revalidation does not re-fetch correctly (the bug just uses in-memory cache again) when deployed. :repro: → https://github.com/lostip/nextjs-revalidation-demo/tree/main --------- Co-authored-by:
Ethan Arrowood <ethan@arrowood.dev>
-
Donny/강동윤 authored
### What? Skip one test completely ### Why? To make CI green ### How? Closes PACK-2921
-
Zack Tanner authored
### What When submitting a server action on a page that doesn't import the action handler, a "Failed to find server action" error is thrown, even if there's a valid handler for it elsewhere. ### Why Workers for a particular server action ID are keyed by their page entrypoints, and the client router invokes the current page when triggering a server action, since it assumes it's available on the current page. If an action is invoked after the router has moved away from a page that can handle the action, then the action wouldn't run and an error would be thrown in the server console. ### How We try to find a valid worker to forward the action to, if one exists. Otherwise it'll fallback to the usual error handling. This also adds a header to opt out of rendering the flight tree, as if the action calls a `revalidate` API, then it'll return a React tree corresponding with the wrong page. Fixes #61918 Fixes #63915 Closes NEXT-2489
-
mknichel authored
This PR adds a `--experimental-debug-memory-usage` flag to `next build` to make it easier to debug memory performance. This mode does the following things: - Periodically prints the current memory usage of the process - Records garbage collection events and warns about long running GC events - Kills the process if it detects GC thrashing near heap limit - Automatically takes a heap snapshot if heap usage rises above 70% of the total heap - Automatically takes a heap snapshot if the process is close to running out of memory - Prints a report at the end of the build with information about peak memory usage and time spent in garbage collection --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Jiachi Liu authored
Currently acornjs has an issue with compiling undici, add undici externalize, once it's resolved we can remove the externalization for it ``` You may need an additional loader to handle the result of these loaders. | // 5. If object is not a default iterator object for interface, | // then throw a TypeError. > if (typeof this !== 'object' || this === null || !(#target in this)) { | throw new TypeError( | `'next' called on an object that does not implement interface ${name} Iterator.` Import trace for requested module: ../../../../node_modules/.pnpm/undici@6.12.0/node_modules/undici/lib/web/fetch/util.js ../../../../node_modules/.pnpm/undici@6.12.0/node_modules/undici/lib/web/fetch/headers.js ../../../../node_modules/.pnpm/undici@6.12.0/node_modules/undici/index.js ./app/undici/page.js ``` Closes NEXT-3030 -
Donny/강동윤 authored
### What? Fix CI, which is broken due to https://github.com/vercel/next.js/pull/58534 ### Why? The PR was out of sync and CI didn't check turbo build ### How? Closes PACK-2920
-
Tobias Koppers authored
### What? align `@opentelemetry/api` alias with webpack ### Why? ### How? Closes PACK-2914 --------- Co-authored-by:Dima Voytenko <dima.voytenko@vercel.com>
-
Donny/강동윤 authored
### What? Add `AbortSignal` to the reserved list of the name mangler. ### Why? We don't want `node-fetch` to throw an exception. x-ref: https://vercel.slack.com/archives/C04KC8A53T7/p1700123182211619?thread_ts=1700090771.304599&cid=C04KC8A53T7 ### How? This PR modifies the mangle option from the Rust side code. Closes PACK-1977
-
- 08 Apr, 2024 14 commits
-
-
vercel-release-bot authored
-
Sebastian Silbermann authored
-
Jiachi Liu authored
x-ref: https://github.com/vercel/next.js/actions/runs/8598454715/job/23559349141?pr=64110 Follow up for #64141 Closes NEXT-3028
-
HyunJick Lee authored
I'm looking at the example code and demo for the Image component, [Responsive image using a static import](https://nextjs.org/docs/app/api-reference/components/image#responsive-image-using-a-static-import) and [Responsive image with aspect ratio](https://nextjs.org/docs/app/api-reference/components/image#responsive-image-with-aspect-ratio) sections are immersive because the code in the example and the demo match, The [Responsive image with fill](https://nextjs.org/docs/app/api-reference/components/image#responsive-image-with-fill) section breaks the immersion because the code in the example and the demo are slightly different. I think it's just a typo. It seems the width and height values are reversed. Attach the code from the demo. <img width="504" alt="Responsive image with fill demo code" src="https://github.com/vercel/next.js/assets/56260102/72ab314d-a9b3-4a88-8d9c-48f0dde8c19f"> Co-authored-by:
Steven <steven@ceriously.com>
-
Benjamin Woodruff authored
I'm not sure why this issue is impacting me and seemingly not others, but on Debian 12 with the default linker options (gcc with ld) I get the following compilation error regarding unresolved symbols: https://gist.github.com/bgw/92da94f46b0994514a144b8938aa2f6c This flag downgrades that linker error to a warning (which cargo hides). I've checked that this flag is supported by ld, gold, lld, and mold. I've also tried building with mold in addition to ld. I'm restricting the option to linux to avoid potentially breaking other platforms. Tested by running: ``` cargo test -p next-swc-napi ``` Which now gives: ``` running 2 tests test transform::test_deserialize_transform_regenerator ... ok test transform::test_deser ... ok ```
-
Jiachi Liu authored
### What We introduced a new algorithm to find the matched hydration error tags, when there're two tags indicating children and parent as bad descendence relationship. Now we search for the child first from the last index, and then from found child to search its above parent. This way we can find the two related tags in O(1), since they could be not directly nested. ### Why When a hydration error occurred, such as bad nesting `div` under `p`, one of the tag `div` is matched multiple times in the component stack, it shouldn't be highlighted multiple times. This PR fixes the bad matching about multiple nested tags, e.g. when there're many `div` tag and `div` is one of the bad tag, only the one directly under p should be highlited. Case ``` Page > div > div > p > div ``` Current Result: all `div` and `p` get highlighted, `[]` represents highlighted. ``` Page > [div] > [div] > [p] > [div] ``` Expected: only the related 2 tags are highlighted, `[]` represents highlighted. ``` Page > div > div > [p] > [div] ``` Thanks @JohnPhamous for reporting the issue Closes NEXT-3022
-
Jiwon Choi authored
### Why? The examples `with-apollo` and `with-graphql-hooks` included outdated API endpoints and packages. This resulted in the **failed Vercel Deployment** of the examples. <details><summary>Screenshot of failed deployments</summary> <p> #### with-graphql-hooks  #### with-apollo  </p> </details> ### How? - Migrated examples from `pages` to `app` router and removed invalid API endpoints. - Refactored the example to a minimal template as possible with essential features. Closes #9865 #10253 #36112 --------- Co-authored-by:
Sam Ko <sam@vercel.com>
-
Donny/강동윤 authored
### What? Synchronize dependencies with turbopack ### Why? This mismatches seem to cause some strange build failures. ### How? Closes PACK-2910
-
Tim Neutkens authored
## What? Few more links for relevant concepts. <!-- 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 # --> Closes NEXT-3027
-
Zack Tanner authored
When we seed the prefetch cache with an entry for the loaded page, we should also mark `lastUsedTime` to be the current time. Otherwise, if the prefetch entry has technically expired, it'll incorrectly be considered "reusable" because the `lastUsedTime` will be set to when it's first routed to client-side. x-ref: https://github.com/vercel/next.js/discussions/54075#discussioncomment-9031149 <!-- 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 # --> Closes NEXT-3025
-
Lee Robinson authored
https://bugs.webkit.org/show_bug.cgi?id=252413 --------- Co-authored-by:
Steven <steven@ceriously.com>
-
Julius Marminge authored
Fixes #64018 Adds support for modern configurations introduced in TS 5.4 Expected output: not modifying the `module`, `esModuleInterop` configs since `module: preserve` is present ``` We detected TypeScript in your project and reconfigured your tsconfig.json file for you. Strict-mode is set to false by default. The following suggested values were added to your tsconfig.json. These values can be changed to fit your project's n eeds: - lib was set to dom,dom.iterable,esnext - allowJs was set to true - skipLibCheck was set to true - strict was set to false - noEmit was set to true - incremental was set to true - include was set to ['next-env.d.ts', '**/*.ts', '**/*.tsx'] - exclude was set to ['node_modules'] The following mandatory changes were made to your tsconfig.json: - isolatedModules was set to true (requirement for SWC / Babel) - jsx was set to preserve (next.js implements its own optimized jsx transform) ``` --------- Co-authored-by:Jiachi Liu <inbox@huozhi.im>
-
Tim Neutkens authored
## What? We're currently seeing a failure on this action but it's unclear why it happens so this PR introduces additional logs. Current failure: https://github.com/vercel/next.js/actions/runs/8550039767/job/23427388195#step:4:110 <!-- 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 # --> Closes NEXT-3024
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing Turbopack.
-