Bryan Nguyen
67acc5ac4d
Correct prop name in server-actions.mdx ( #58108 )
...
Code snippet below line changed uses `myAction`
2023-11-06 21:54:45 +00:00
vercel-release-bot
c29c039cf3
v14.0.2-canary.15
2023-11-06 20:56:03 +00:00
Wyatt Johnson
ffeaa8f366
fix: normalization and invariant fixes for ppr ( #58105 )
2023-11-06 20:51:06 +00:00
Justin Ridgewell
030021234b
Adjust update-turbopack-test-manifest.yml to run once per day ( #58104 )
...
The workflow is creating and closing PRs ever hour, which is too much.
2023-11-06 14:51:35 -05:00
Justin Ridgewell
26d9343419
Fix update-turbopack-test-manifest.yml workflow ( #58097 )
...
https://github.com/vercel/next.js/actions/runs/6774028544/job/18410200888#step:4:35
2023-11-06 12:31:11 -05:00
vercel-release-bot
38e8b523dc
v14.0.2-canary.14
2023-11-06 17:08:35 +00:00
Tobias Koppers
883ab22157
update turbopack ( #58080 )
...
* https://github.com/vercel/turbo/pull/6325 <!-- OJ Kwon - build(cargo):
skip external build script with rust-analyzer -->
* https://github.com/vercel/turbo/pull/6318 <!-- OJ Kwon -
feat(turbopack-ecmascript): calculate import.meta.url as an absolute
path -->
* https://github.com/vercel/turbo/pull/6359 <!-- Will Binns-Smith -
Turbopack: Defer calculating source positions until needed -->
* https://github.com/vercel/turbo/pull/6274 <!-- Tobias Koppers - add
backtrace for trait calls -->
* https://github.com/vercel/turbo/pull/6305 <!-- Tobias Koppers - Triple
chunk size heuristic -->
* https://github.com/vercel/turbo/pull/6304 <!-- Tobias Koppers -
improve resolving performance -->
2023-11-06 18:05:13 +01:00
Dominic Elm
103ca04688
feat: always use SWC Wasm fallback when running in WebContainer ( #58081 )
...
<!-- 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?
Since the Wasm fallback was re-introduced in
https://github.com/vercel/next.js/pull/57906 I am now also adding a
check for detecting WebContainers so that it would always use the SWC
Wasm fallback. That's because WebContainers can't execute native
binaries.
I decided to not account for `NEXT_DISABLE_SWC_WASM` because it doesn't
make much sense and if someone had this enabled, it would always fail.
But if ya all think it's better to take this flag into account then I am
happy to change it.
2023-11-06 11:38:26 -05:00
Tobias Koppers
8220976d29
fixes a problem with cache invalidation ( #58079 )
...
### What?
fixes a problem with cache invalidation when the next.js folder moves in node_modules, but the version stays equal
### Why?
This can happen when pnpm creates a new next.js copy with different peerDependencies.
2023-11-06 13:56:04 +00:00
Tobias Koppers
99e584c70e
use __NEXT_VERSION compile time replacement ( #57512 )
...
process.env.__NEXT_VERSION is replaced at with a static version
Closes WEB-1888
2023-11-06 08:55:33 +00:00
vercel-release-bot
31c2f976cd
v14.0.2-canary.13
2023-11-05 23:23:20 +00:00
Md Rashidul Islam
7feede955f
docs: useFormState and useOptimistic are now documented ( #58064 )
...
Co-authored-by: Lee Robinson <9113740+leerob@users.noreply.github.com>
2023-11-05 22:09:12 +00:00
Tim Neutkens
f0f3aa5fd5
Fix options of createNextInstall ( #58036 )
...
Noticed there was some default assignment to `null` for e.g. `rootSpan`
but that paremeter is not optional. Fixed that and did some small
refactoring.
<!-- 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 #
-->
2023-11-05 20:33:36 +01:00
Tim Neutkens
aedd858598
Fix should have correct module not found error test ( #57383 )
...
The module not found check is a bit different in Turbopack.
<!-- 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 #
-->
2023-11-05 18:57:21 +01:00
Tim Neutkens
e648b48e8d
Remove installCommand on typescript-auto-install and pnpm-support ( #58039 )
...
Similar to #58037 . Removes `installCommand` where it's not needed.
<!-- 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 #
-->
2023-11-05 18:32:10 +01:00
Tim Neutkens
734eeac613
Use distDir from webpack-config in createWebpackAliases ( #57268 )
...
distDir is available in the place where we'll call this function for
Turbopack so it can be passed in.
<!-- 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 #
-->
2023-11-05 16:36:13 +01:00
Tim Neutkens
bafa8d4948
Remove installCommand on streaming-ssr test ( #58037 )
...
Removes installCommand as it doesn't have to be different than the
default command. Also converted to using `createNextDescribe`.
<!-- 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 #
-->
2023-11-05 13:30:12 +01:00
vercel-release-bot
8536ad98dd
v14.0.2-canary.12
2023-11-04 23:21:06 +00:00
Tim Neutkens
b9baf48257
Remove setPnpmResolutionMode as default is highest ( #57828 )
...
The linked documentation mentions that `highest` is the default in the
pnpm version we use:
> Default: highest (was lowest-direct from v8.0.0 to v8.6.12)
https://pnpm.io/npmrc#resolution-mode
<!-- 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: Zack Tanner <zacktanner@gmail.com>
2023-11-04 21:19:51 +01:00
Tim Neutkens
758c47f801
use createNextDescribe for test/development/basic tests ( #58031 )
...
Converted some additional tests to `createNextDescribe`.
<!-- 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 #
-->
2023-11-04 20:02:34 +01:00
Wyatt Johnson
6c6ac700b2
fix: ensure that postponed requests can be resumed in minimal mode ( #58011 )
2023-11-04 00:21:18 +00:00
Zack Tanner
54a0e05309
tweak stats action to pull in runtime sizes ( #58005 )
...
This wasn't working previously so updated the glob & script to properly track changes to our bundled next runtimes
Should now be appended to the bottom of the PR stats action, eg:
2023-11-03 23:39:37 +00:00
vercel-release-bot
d0ac7c2f45
v14.0.2-canary.11
2023-11-03 23:22:55 +00:00
Lee Robinson
100eea486a
docs: Revert part of sitemap docs change ( #58010 )
...
Revert part of https://github.com/vercel/next.js/pull/57998 .
2023-11-03 18:10:16 -05:00
Wyatt Johnson
3fa9f31ce1
fix: updates for resuming postponed in minimal mode ( #57375 )
...
Co-authored-by: Jimmy Lai <11064311+feedthejim@users.noreply.github.com>
2023-11-03 21:17:45 +00:00
Yusril A
b8b1ec24a2
docs: improve non-encrypted HTTP conn to a secure ( #57998 )
2023-11-03 14:51:01 -05:00
vercel-release-bot
ffdfd33251
v14.0.2-canary.10
2023-11-03 12:13:32 +00:00
Tim Neutkens
4a89febf97
Improve CSRF protection error in Server Actions ( #57980 )
...
Follow-up to #57529 , this adds extra logging so that you know what the header value was in order to configure it correctly.
2023-11-03 11:40:46 +00:00
Tim Neutkens
7cea497626
Skip webpack only test ( #56929 )
...
One more small tests skipped that is webpack-only.
2023-11-03 01:37:21 +00:00
Thomas Knickman
348c550120
feat(turbo): use turbo gen instead of plop ( #53684 )
...
### What?
Use [Turborepo generators](https://turbo.build/repo/docs/core-concepts/monorepos/code-generation#custom-generators ) instead of plop.
Turborepo generators are built on top of plop, but include some additional tooling to make working in monorepos easier. It also supports zero config typescript for configs.
### Why?
Same Team!
### How?
Ported the existing plopfile to a turbo generator config
Co-authored-by: Jiachi Liu <4800338+huozhi@users.noreply.github.com>
2023-11-03 01:25:18 +00:00
Tim Neutkens
520fbc884d
Remove throw for unknown messages in hot-reloader-client ( #57353 )
...
Ensures extra messages are ignored instead of throwing an error.
2023-11-03 01:06:53 +00:00
Lee Robinson
53b684a795
docs: Update MDX docs title. ( #57963 )
...
To better match both keywords.
2023-11-02 19:54:49 -05:00
Chenguang Li
067ff4e978
Update 05-mdx.mdx ( #57866 )
...
One more `
2023-11-03 00:54:21 +00:00
Vũ Văn Dũng
0baafc727b
Improve grammar of removable Babel config warning ( #55088 )
...
The current warning is
> It looks like there is a custom Babel configuration can be removed .
which in this PR is updated to
> It looks like there is a custom Babel configuration that can be removed.
---
[Original bug found by @protehnica on the Next.js Discord:](https://discord.com/channels/752553802359505017/1148942305194152056 )
> On my server I used to have a `.babelrc` file to disable `@next/swc`, because it wouldn't run on CentOS 7.
> Apparently this is no longer needed now in Next.js 13, but the message warning users about it looks extremely unprofessional.
>
> > "It looks like there is a custom Babel configuration can be removed ."
>
> Not only is the grammar off, there's also a weird space before the final dot.
> Can someone who's already working on the codebase submit a pull request?
> I would love to do it myself, but I wouldn't know where to start.
>
> The exact file in the repo containing the message string is:
> ```next.js/packages/next/src/build/babel/loader/get-config.ts```
2023-11-03 00:51:53 +00:00
Jimmy Lai
82d1b57721
misc: fix serverComponentsExternalPackages usage for experimental.bundlePagesExternals ( #57954 )
...
This PR fixes a bug where Next.js would not use the serverComponentsExternalPackages config when opting into the `experimental.bundlePagesExternals` flag.
The fix consists of just adding a check for the externals config.
2023-11-02 23:57:52 +00:00
vercel-release-bot
8014866cac
v14.0.2-canary.9
2023-11-02 23:21:41 +00:00
Jiachi Liu
9af75d4b2d
Fix client chunk loading encoding for dynamic route ( #57960 )
...
We had added encoding the client component assets loaded from RSC manifest that we need to encode them to make sure when they're loaded on server and sent to client, the client will receive the encoded one. But the override of the webpack chunk loading method could be loaded later than react related chunks, that when client component is loaded first (e.g. `next/script`) and it triggers react loaded ealier than the overriding. Then the chunk could be encoded incorrectly.
Discussed with @gnoff and put this out as the 1st step solution to ensure the order. in the future we can try to get rid of the encoding by providing safer url
Fixes #57829
2023-11-02 23:09:25 +00:00
Will Binns-Smith
c95ef234fc
Move ReactRefreshLogBox-builtins tests to inline snapshots ( #57952 )
...
This avoids separate snapshots for both Turbopack and Webpack, and correctly reflects that these fail.
2023-11-02 21:32:52 +00:00
OJ Kwon
6f8c580386
feat(turbopack): Experimental wasm build ( #57906 )
...
### What?
continuation of https://github.com/vercel/next.js/pull/57851 , since it is from a remote branch that I don't have access to write.
Co-authored-by: Maia Teegarden <2865858+padmaia@users.noreply.github.com>
Co-authored-by: Tim Neutkens <6324199+timneutkens@users.noreply.github.com>
2023-11-02 21:00:54 +00:00
vercel-release-bot
f979341f82
v14.0.2-canary.8
2023-11-02 20:34:16 +00:00
Zack Tanner
5da8ad7baf
move static worker IPC server behind experimental flag ( #57943 )
...
A shared incremental cache IPC server was introduced for build-time static workers as an optimization to dedupe fetch requests, however this can cause fetch-related flakiness to builds under certain conditions (e.g., large payloads).
This moves the optimization behind an experimental flag to unblock those running into IPC-related build time errors while we work on an alternative solution for the underlying issue
Fixes #53695
2023-11-02 20:26:55 +00:00
vercel-release-bot
ad55d78199
v14.0.2-canary.7
2023-11-02 19:59:43 +00:00
Zack Tanner
85abc48c90
suspend in render, not in reducers ( #56497 )
...
This removes our current convention of throwing promises in reducers in
favor of returning promises that can be consumed by `use` instead. This
will help unblock some future improvements (batching, PPR)
Reducers that would typically throw a promise now return their promise.
This gets maintained by a mutable queue (initialized in hydrate) to
ensure actions are processed in-order. The queue is also responsible for
mutating state and passing it as an input to subsequent actions.
This PR does not modify reducer behavior to keep changes minimal, but
there's more cleanup that we can do in a follow-up PR to remove things
that previously assumed reducers would be replayed.
(I recommend reviewing with whitespace turned off)
---------
Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
2023-11-02 11:53:50 +01:00
Steven
be618048fe
chore(test): run unit tests on node 18 and 20 ( #57199 )
...
Since we separated unit tests into its own job in PR https://github.com/vercel/next.js/pull/55621 , we can now run unit tests against Node.js 18 and Node.js 20 (maintenance and lts) using a matrix.
2023-11-02 10:43:18 +00:00
vercel-release-bot
1c5d7782a0
v14.0.2-canary.6
2023-11-01 23:21:29 +00:00
Wyatt Johnson
13f0303085
Reduce FS access for incremental cache ( #57902 )
...
This passes down the route kind information to the incrememntal cache so it no longer needs to test some files existing in order to validate if the file exists or not for a route.
2023-11-01 21:17:16 +00:00
Zack Tanner
7b524fa2d3
ppr: fail static generation if postponed & missing postpone data ( #57786 )
...
When postpone is caught by user code, this will cause PPR not to properly prerender the static parts and thus we need to fail the build. This also adds some messaging about how to fix the error.
Prior to this change, catching code that would normally trigger `postpone ` would silently fail, but the build outputs would be incorrect as there's no postpone data available.
Relands #57477 with additional tests & fixes
2023-11-01 20:28:13 +00:00
Balázs Orbán
1b0113bfea
chore: remove redundant jest config ( #57151 )
...
### What?
Drop redundant Jest config
### Why?
This slipped in by accident. It's already the default value. See https://jestjs.io/docs/configuration#snapshotformat-object
2023-11-01 20:18:57 +00:00
OJ Kwon
555b13180e
fix(next-core): externalcjs resolve options ( #57645 )
...
### What
Probably not a big deal since we run this against cjs / esm both, but looks like it's a minor typo.
Closes WEB-1894
2023-11-01 19:38:17 +00:00
Jiachi Liu
62267ec7c7
remove legacy handling for suspense option of next/dynamic ( #57900 )
...
This part was removed before but added in back during the merging of turbopack and legacy `next-swc` changes. Remove them again
2023-11-01 17:47:32 +00:00
