Commits

Closes #59310, see attached test cases. Closes NEXT-1830

### What? Update SWC crates. ### Why? To fix OOM bug of `inputSourceMap`. Patch: swc-project/swc#8402 ### How? Closes PACK-2123 # Turbopack updates * vercel/turbo#6733  * vercel/turbo#6731  * vercel/turbo#6745

### What? switch turbopack to use a single client components entrypoint for all client components on a page for development. This aligns it with the webpack behavior. ### Why? compiling a separate entrypoint for every client component is pretty expensive in regards of compilation, chunking, code generation, file writing and number of requests. ### Turbopack Changes * vercel/turbo#6713  * vercel/turbo#6728  Closes PACK-2115

…58902)

- [x] Rename page from `forms-and-mutations` to `server-actions-and-mutations` to account for examples that don't use forms. - [x] Split `/pages` and `/app` content to make easier to edit - [x] Add Security Section - [x] Recommend tainting - [x] Closures and encryption - [x] Overwriting encryption keys - [x] CSRF protection | Allowed Origins - [x] Add examples for Server Actions being called outside forms - [x] `useEffect` - [x] Event handlers - [ ] ~3rd party libraries~ - [x] More form examples - [x] Add note on calling actions in `<button>` and `<input> ` - [x] Add `.bind` example | Recommend bind over hidden input field - [x] Recommend `try/catch` for error handling - [x] Create `serverActions` next.config.js page - [x] Document `allowedOrigins` - [x] Document `bodySizeLimit` - [x] Add note on Server Actions flag for < v14 - [x] Update error message links - [x] Remove Server Actions from API reference as it's a React feature. E.g. We don't have API references for Server Components. - [ ] Set up redirects: --------- Co-authored-by: Lee Robinson <me@leerob.io> Co-authored-by: Shu Ding <g@shud.in> Co-authored-by: Michael Novotny <manovotny@gmail.com>

fixes #58087 Currently in Next 14, everyone has fullURL flag turned to true, this PR reverts the condition. --------- Co-authored-by: Jiachi Liu <inbox@huozhi.im>

Fixes ability to run `NODE_OPTIONS='--inspect' next dev` as described in [docs](https://nextjs.org/docs/pages/building-your-application/configuring/debugging), by removing inspect option from NODE_OPTIONS arg passed to worker process. This bug seem to have been introduced in 7d93808 as a part of a some refactoring. See how `getNodeOptionsWithoutInspect` is no longer used. Fixes #55862 --------- Co-authored-by: Jiachi Liu <inbox@huozhi.im>

@alvarlagerlof

### What? While scrolled on a page, and when following a link to a new page and clicking the browser back button or using `router.back()`, the scroll position would sometimes restore scroll to the incorrect spot (in the case of the test added in this PR, it'd scroll you back to the top of the list) ### Why? The refactor in #56497 changed the way router actions are processed: specifically, all actions were assumed to be async, even if they could be handled synchronously. For most actions this is fine, as most are currently async. However, `ACTION_RESTORE` (triggered when the `popstate` event occurs) isn't async, and introducing a small amount of delay in the handling of this action can cause the browser to not properly restore the scroll position ### How? This special-cases `ACTION_RESTORE` to synchronously process the action and call `setState` when it's received, rather than creating a promise. To consistently reproduce this behavior, I added an option to our browser interface that'll allow us to programmatically trigger a CPU slowdown. h/t to @alvarlagerlof for isolating the offending commit and sharing a minimal reproduction. Closes NEXT-1819 Likely addresses #58899 but the reproduction was too complex to verify.

This auto-generated PR updates the integration test manifest used when testing Turbopack.

## What? - Add support for `experimental.externalDir` -- Was already supported, just makes Turbopack not fail on that config option - Skipped `with-babel` test because it tests Babel - Skipped `swc-warnings` test because it tests Babel - Skipped `config-resolve-alias` as it tests webpack config - Skipped `undefined-webpack-config` as it tests webpack config  Closes NEXT-1817

Co-authored-by: Jiachi Liu <inbox@huozhi.im>

### What? Visiting an edge catch-all route incorrectly truncates multiple parameters ### Why? The params are currently coerced into a `ParsedURLQuery`-like format by calling `Object.fromEntries` on `searchParams`, but this doesn't consider multiple param values assigned to the same key ### How? Rather than use `fromEntries`, this uses an existing util to get the path into `ParsedURLQuery` format. Closes NEXT-1814 Fixes #59333

### What? When running a [multi-zone](https://github.com/vercel/next.js/tree/canary/examples/with-zones) app in dev, app pages would infinitely reload ### Why? The HMR upgrade request would fail and get caught into a retry loop. In the multi-zone case, they fail because the upgrade request would be sent again for a request that had already been upgraded. This resulted in a "server.handleUpgrade() was called more than once with the same socket" error, causing the upgrade request to fail. Every time a retry occurred, the page would trigger a full refresh since certain HMR errors cause the browser to reload. ### How? This ensures the upgrade handler only responds to requests that match the configured basePath. Closes NEXT-1797 Fixes #59161 Fixes #56615 Fixes #54454

### What? remove expensive unused code Closes PACK-2108

* vercel/turbo#6716  * vercel/turbo#6718

This auto-generated PR updates the integration test manifest used when testing Turbopack.

### What? Reduce the number of function calls ### Why? Performance on incremental builds ### How? Closes PACK-2104

## What? Noticed constants.js was included in the client-side bundle. This ensures only the needed constants are included. ## How? Created a separate file for client-side constants.  Closes NEXT-1789

### What? Code update for refactoring in vercel/turbo#6590 Closes PACK-2043

) ### What? add tracing to the module graph walking Closes PACK-2090

This is a continuation from #58783 to remove the remaining code related to static prefetching.

Commits on Dec 8, 2023

Commits on Dec 7, 2023

Commits on Dec 6, 2023