* Fix React Refresh boundary finding

We forgot to enable the transform, which means we were rendering from the root of the app instead of the changed component.

* Update snapshots

* Add comment

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

…bo#2586)

* fixup ropes

* add RSC and RCC for turbopack to benchmarks

RSC: whole page is a server component
RCC: whole page is a client component

add `app` directory to test app

* bugfix source maps in app dir

* add specificity

static assets are preferred over dynamic matches

* add different keyed app route elements

* update for latest next.js canary version

* fix header name

* setup next.js version in benchmark

…turbo#2653)

Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>

* retry setup steps if needed

* retry install nextest step

* retry browser launch

* ignore errors from PR comment failing due to PR from fork

This PR changes the ecmascript chunk logic to polyfill `global` with `globalThis`. A more complex and less performant solution (but with the benefit of us knowing the runtime environment) would be to add an effect for simple identifier expressions.

* use iterations feature from criterion

move startup, warmup and teardown out of the iteration loop to avoid tracking this time as elapsed time
this allows criterion to use the measurement time correctly for the measured task

prefer slope over mean when possible as it estimates the real time (excluding warmup)

* remove warmup argument

* stop server for next iteration

* refactor

* restore verbose info, exclude file read from timing

* add a little bit of delay between HMR updates

* make a warmup change

* no need to copy template dir for HMR benchmark

* add delay after warmup change

* add watch benchmark

* add/fix comments

* fix env var in CI

measure hmr_to_commit with detector component

add Next.js 13 to benchmarks with RSC and RCC measurements

this tests RSC HMR

make HMR warmup faster

make browser launch lazy

test benchmarks for other bundlers on CI too

# Conflicts:
#	.github/workflows/test.yml
#	crates/next-dev/benches/mod.rs

…turbo#2830)

* pull upstream changes

* ts fixes

)

* Sample many modules in benchmarks + reliability fixes

* Fix depth sampling to be uniform

* Fix Webpack benchmark

* Only use detector component for RSC

* Clippy

* Clippy

* build(cargo): setup next-binding package

* build(cargo): update dependencies

* style(toml): update config

* ci(actions): check next-binding

* feat(next-binding): reexports

* build(cargo): update lockfile

Commit 1: It took me hours to figure out this unsafe problem...

Commit 2: updates tokio

Commit 3: improves hanging detection to allow to attach notes to event listeners

* Make task stats take less memory by default

* Swap order of condition operands

* TaskStats -> ExportedTaskStats

* Add full stats disclaimers

* Clippy

* Fix duplicate labels

* Move stats type reporting to TurboTasks

* Fix turbotrace and turbopack visualization

* Store last duration and execution as SmallDurations

Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>

* refactor exports

* tabs + styles + icons

* Add GitHub action step for taplo --check

* Run taplo format

This implements basic support for serving the images requested by `next/image` and `next/future/image`. The big missing features are:

- image width resizing (and thus blurry image placeholders)
- image quality encoding
- format re-encoding

This required a lot more work than I expected, because we have to also override the `remotePatterns` to allow using `next/image` with remote images. The only way I found to do this was to override the `__NEXT_IMAGE_OPTS` env var, which is a special object value injected by webpack's `DefinePlugin` as if it were an `process.env` value.

Fixes https://github.com/vercel/web-tooling-internal/issues/5
Porting from https://github.com/vercel/the-three-body/pull/212
Fixes WEB-150
Fixes WEB-2

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [futures](https://rust-lang.github.io/futures-rs) ([source](https://togithub.com/rust-lang/futures-rs)) | dev-dependencies | patch | `0.3.21` -> `0.3.25` |
| [futures](https://rust-lang.github.io/futures-rs) ([source](https://togithub.com/rust-lang/futures-rs)) | dependencies | patch | `0.3.21` -> `0.3.25` |
| [futures](https://rust-lang.github.io/futures-rs) ([source](https://togithub.com/rust-lang/futures-rs)) | dependencies | patch | `0.3.24` -> `0.3.25` |

---

### ⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

### Release Notes

<details>
<summary>rust-lang/futures-rs</summary>

### [`v0.3.25`](https://togithub.com/rust-lang/futures-rs/blob/HEAD/CHANGELOG.md#&vercel/turbo#8203;0325---2022-10-20)

[Compare Source](https://togithub.com/rust-lang/futures-rs/compare/0.3.24...0.3.25)

-   Fix soundness issue in `join!` and `try_join!` macros ([#&vercel/turbo#8203;2649](https://togithub.com/rust-lang/futures-rs/issues/2649))
-   Implement `Clone` for `sink::Drain` ([#&vercel/turbo#8203;2650](https://togithub.com/rust-lang/futures-rs/issues/2650))

### [`v0.3.24`](https://togithub.com/rust-lang/futures-rs/blob/HEAD/CHANGELOG.md#&vercel/turbo#8203;0324---2022-08-29)

[Compare Source](https://togithub.com/rust-lang/futures-rs/compare/0.3.23...0.3.24)

-   Fix incorrect termination of `select_with_strategy` streams ([#&vercel/turbo#8203;2635](https://togithub.com/rust-lang/futures-rs/issues/2635))

### [`v0.3.23`](https://togithub.com/rust-lang/futures-rs/blob/HEAD/CHANGELOG.md#&vercel/turbo#8203;0323---2022-08-14)

[Compare Source](https://togithub.com/rust-lang/futures-rs/compare/0.3.22...0.3.23)

-   Work around MSRV increase due to a cargo bug.

### [`v0.3.22`](https://togithub.com/rust-lang/futures-rs/blob/HEAD/CHANGELOG.md#&vercel/turbo#8203;0322---2022-08-14)

[Compare Source](https://togithub.com/rust-lang/futures-rs/compare/0.3.21...0.3.22)

-   Fix `Sync` impl of `BiLockGuard` ([#&vercel/turbo#8203;2570](https://togithub.com/rust-lang/futures-rs/issues/2570))
-   Fix partial iteration in `FuturesUnordered` ([#&vercel/turbo#8203;2574](https://togithub.com/rust-lang/futures-rs/issues/2574))
-   Fix false detection of inner panics in `Shared` ([#&vercel/turbo#8203;2576](https://togithub.com/rust-lang/futures-rs/issues/2576))
-   Add `Mutex::lock_owned` and `Mutex::try_lock_owned` ([#&vercel/turbo#8203;2571](https://togithub.com/rust-lang/futures-rs/issues/2571))
-   Add `io::copy_buf_abortable` ([#&vercel/turbo#8203;2507](https://togithub.com/rust-lang/futures-rs/issues/2507))
-   Remove `Unpin` bound from `TryStreamExt::into_async_read` ([#&vercel/turbo#8203;2599](https://togithub.com/rust-lang/futures-rs/issues/2599))
-   Make `run_until_stalled` handle self-waking futures ([#&vercel/turbo#8203;2593](https://togithub.com/rust-lang/futures-rs/issues/2593))
-   Use `FuturesOrdered` in `try_join_all` ([#&vercel/turbo#8203;2556](https://togithub.com/rust-lang/futures-rs/issues/2556))
-   Fix orderings in `LocalPool` waker ([#&vercel/turbo#8203;2608](https://togithub.com/rust-lang/futures-rs/issues/2608))
-   Fix `stream::Chunk` adapters size hints ([#&vercel/turbo#8203;2611](https://togithub.com/rust-lang/futures-rs/issues/2611))
-   Add `push_front` and `push_back` to `FuturesOrdered` ([#&vercel/turbo#8203;2591](https://togithub.com/rust-lang/futures-rs/issues/2591))
-   Deprecate `FuturesOrdered::push` in favor of `FuturesOrdered::push_back` ([#&vercel/turbo#8203;2591](https://togithub.com/rust-lang/futures-rs/issues/2591))
-   Performance improvements ([#&vercel/turbo#8203;2583](https://togithub.com/rust-lang/futures-rs/issues/2583), [#&vercel/turbo#8203;2626](https://togithub.com/rust-lang/futures-rs/issues/2626))
-   Documentation improvements ([#&vercel/turbo#8203;2579](https://togithub.com/rust-lang/futures-rs/issues/2579), [#&vercel/turbo#8203;2604](https://togithub.com/rust-lang/futures-rs/issues/2604), [#&vercel/turbo#8203;2613](https://togithub.com/rust-lang/futures-rs/issues/2613))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about these updates again.

---

 - [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/vercel/turbo).

updating in hope that this fixes the random errors in test runs

…#2743)

* Add query structure to module requests

* Update crates/next-dev/src/lib.rs

Co-authored-by: Justin Ridgewell <justin@ridgewell.name>

Co-authored-by: Justin Ridgewell <justin@ridgewell.name>

* Check in next-font transform from Next.js repo

* Use next-font transform

* Run transform via custom rule

* Place next/font transform behind cargo feature

* Remove unused dependencies

* Add back lazy static as a dev dep

* Add back bench dependencies

…rls (vercel/turbo#2856)

* Implement get_font_axes

* Implement get_stylesheet_url

* Handle font axes without wght

Co-authored-by: Hannes Bornö <hannes.borno@vercel.com>

* Implement extract_font_urls

* Update crates/next-core/src/next_font_google/util.rs

Co-authored-by: Justin Ridgewell <justin@ridgewell.name>

* Remove extraction of fonts

Co-authored-by: Hannes Bornö <hannes.borno@vercel.com>
Co-authored-by: Justin Ridgewell <justin@ridgewell.name>

* Add font-data.json

* Initial implementation of dynamic ImportMapping replacement

* Extract font urls

* Download fonts

* Update stylesheet

* Vc-ify

* Apply suggestions from code review

Co-authored-by: Alex Kirszenberg <alex.kirszenberg@vercel.com>

* Check in font-data.json update script and update font-data.json

* Add font update to ci schedule

* assert -> bail

* Remove extraction and caching of fonts

Co-authored-by: Alex Kirszenberg <alex.kirszenberg@vercel.com>

* Run setup-node in update-google-fonts workflow

* Update Google font-data.json (ce83bb98897404b791fd96f562a95fc0b20b40da)

Co-authored-by: wbinnssmith <wbinnssmith@users.noreply.github.com>

* Initial implementation of FetchIssue

* turbo-tasks-fetch: Emit issues for failed fetches

* Use FetchResult and handle failure in `@next/font/google`

* Apply suggestions from code review

Co-authored-by: Leah <github.leah@hrmny.sh>

Co-authored-by: Leah <github.leah@hrmny.sh>

…t/font/local only (vercel/turbo#2965)

…turbo#2978)

* Implement `DeterministicHash` for `&str`

* @next/font/google: Hash filenames used in virtual file paths

* Apply suggestions from code review

Co-authored-by: Leah <github.leah@hrmny.sh>

Co-authored-by: Leah <github.leah@hrmny.sh>

* Created two separate chains for executing commands: One that uses the parsed arguments from clap that are
serialized to json, the other that still uses Cobra. Now to test to ensure that both do the same thing

* Adjusted json serialization. Now debugging

* Hooked up new CLI to commands

* Fixing compile error

* fixing lint error

* Fixing more Go lint errors

* Fixing lint errors

* fixing up tests

* Only using turbo state with link, login, and logout commands

* Reverting changes

* Removing more changes

* Deleting code and fixing lints

* Removed unlink command

* Fixing bugs

* Reverting more changes

* fixed all tests

* Refactored away duplicates using CLIConfigProvider interface

* Lint fixes

* Minor order tweak

* Added error if command is not handled

* PR feedback

* Minor fixes. Adding --__test-run flag

* Added workaround for subcommand help

* Moved logic around to accomodate login/logout/link/unlink

* Added some documentation, removed some printf

* Adding more tests.

* Hooked up link/login/unlink to --__test-run flag. Also added prysk tests for it.

* Split up derive into multiple lines

* Added comment explaining clap v3 in Cargo.toml

* Ported daemon

* Cleaning up code. Removed imports

* Fix lints

* Fixing lints

* Ported prune to Rust CLI

* Going all the way. Porting run to Rust CLI and upgrading back to clap v4

* Always gotta be testing

* Always be testing. Always. Be. Testing.

* Added tests for each singular flag. Now for combination tests

* WIP: Hooking up Rust CLI to Go run logic

* Disable color

* Removed root inference from Go side

* Fixing compile errors

* Update cli/cmd/turbo/main.go

Co-authored-by: Chris Olszewski <chrisdolszewski@gmail.com>

* Patching up code for run

* PR changes

* Restored labeler

* Restore og.tsx

* Reverted run changes that somehow made it in here

* Fix run

* Update cli/internal/turbostate/turbostate.go

Co-authored-by: Chris Olszewski <chrisdolszewski@gmail.com>

* feat: polyfill `global` with `globalThis` (vercel/turbo#2666)

This PR changes the ecmascript chunk logic to polyfill `global` with `globalThis`. A more complex and less performant solution (but with the benefit of us knowing the runtime environment) would be to add an effect for simple identifier expressions.

* delete IsYarn util (vercel/turbo#2668)

* feat(docs): new authors & consistent filesnames (vercel/turbo#2680)

* Added caveat to environment variables docs (vercel/turbo#2703)

Co-authored-by: Thomas Knickman <tom.knickman@vercel.com>

* Fix publish workflow (vercel/turbo#2681)

* change from yarn to pnpm (vercel/turbo#2686)

Co-authored-by: Justin Ridgewell <justin@ridgewell.name>

* Reverted workflow changes

* Fixing tests. Added run args to base

* Trying to fix tests

* Rewrote some logic around run args handling

* Fixing up tests by adding flags and fixing parsing bugs

* Hooked up RepoState to Go code

* Fixing e2e tests

* Fixing e2e

* Gotta build shim, not turbo in package.json

* Patched integration test

* Reverted Cargo.toml

* Cargo.lock too

* Fixing tests

* Moving turbo binary to shim

* Fixed tests and CI

* Check for TURBO_BINARY_PATH

* Ported shell completions to Rust

* Fixed logic issue with TURBO_BINARY_PATH

* Created .gitignore file with generated rust and header files

* Second try on cleaning up generated files

* More CI fixes

* Realized we still need some inference

* Removed files that are edited by run-examples.sh

* Switched order of `cargo fmt --check` and `cargo clippy` because `cargo clippy` generates files needed for `cargo fmt --check`.

* Cleaning up changes.

* Fix one thing break another

* Accept integration changes

* Deleting more unused code

* Test fixes

* No longer need this line now that src/ffi.rs is gitignored

* PR feedback

* Update cli/internal/run/run.go

Co-authored-by: Chris Olszewski <chrisdolszewski@gmail.com>

* Fixing typo

* Merged main

* PR feedback

* PR feedback

* Merge main

* Reverted workflow change

* Error on invalid unicode instead of lossy conversion

* PR feedback

* Squashed commit of the following:

commit 096b8b8b357abe985e4116108af8a87aaba968cb
Author: David Barrat <david@barrat.io>
Date:   Mon Dec 5 15:29:41 2022 +0100

    Docs: Add Authdog to Turbo Showcase page (vercel/turbo#2921)

    [Authdog](https://www.authdog.com/)  is an Identity and Access Management as a Service platform, built upon Serverless technologies (AWS Lambda, Vercel, Fastly and Cloudflare Workers). I started looking for alternatives to Nx, some times ago and experimented with Turbo, decided to migrate some projects to this tool, awesome stuff!

commit e39d65eb5b97140fe6338dabfbd0ac3be2987d8f
Author: Tobias Koppers <tobias.koppers@googlemail.com>
Date:   Mon Dec 5 15:23:40 2022 +0100

    enable id reusing (vercel/turbo#2895)

    Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

commit 6b99818abd358ebb4fa3506b493e2fae34372d25
Author: Tobias Koppers <tobias.koppers@googlemail.com>
Date:   Mon Dec 5 15:22:53 2022 +0100

    Reduce wrapper tasks by eagerly resolving Vcs (vercel/turbo#2933)

    * resolve codegenerateable before calling it

    * eagerly resolve some constructors to avoid creating many wrapper tasks

    Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

commit ce4c445cd2c17021b4397c8e3cf93d91921146ef
Author: Tobias Koppers <tobias.koppers@googlemail.com>
Date:   Mon Dec 5 15:22:32 2022 +0100

    Share TaskInputs between task cache and task (vercel/turbo#2923)

    Move bound task function into TaskState to allow unloading

    Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

commit e1bf5e2cde7ca2006c8a4c3455dec38e971aa3eb
Author: Tobias Koppers <tobias.koppers@googlemail.com>
Date:   Mon Dec 5 14:32:24 2022 +0100

    make sure that removing collectibles will cleanup helper entries (vercel/turbo#2872)

commit 532eff76326fb9237a450345b45073c1061e5a37
Author: Tobias Koppers <tobias.koppers@googlemail.com>
Date:   Mon Dec 5 13:27:22 2022 +0100

    Reduce the number of Strings and wrapper tasks (vercel/turbo#2834)

    * use Cow to avoid creating Strings for trait function names
    * trait calls avoid the resolve trait wrapper task when called on a resolved VC
    * eagerly resolve some Vc that would otherwise create a lot of wrapper tasks

    Depends on vercel/turbo#2416

commit dc36fc41586e5763520b4a16d249cdd6779bc902
Author: Tobias Koppers <tobias.koppers@googlemail.com>
Date:   Mon Dec 5 11:00:10 2022 +0100

    reduce number of allocations (vercel/turbo#2833)

    VecDeque::new always allocates 7 elements

commit 4f247be94b03f44765ac8bd334194545cd992b9b
Author: Nathan Hammond <nathan.hammond@vercel.com>
Date:   Mon Dec 5 15:39:15 2022 +0800

    Upgrade to Next.js 13 (vercel/turbo#2906)

    This gets our site updated to Next.js 13 and Nextra 2. As a bonus, this should help prevent some of the issues we're seeing in Sentry.

commit 1e818068241c308cd3260bd83eba294d890a6151
Author: Tobias Koppers <tobias.koppers@googlemail.com>
Date:   Mon Dec 5 07:42:19 2022 +0100

    shrink lists and sets that are stored in Tasks (vercel/turbo#2873)

    Reduces memory usage by 14%

commit cac79bbe35c5ee7d2bf14625bb709dff8010b8ad
Author: Ahab <ahabhgk@gmail.com>
Date:   Sun Dec 4 13:23:26 2022 +0800

    make lazy bundling for dynamic import more lazy (vercel/turbo#2918)

    For example:

    ```js
    // index.js
    setTimeout(() => {
      import('./async.js').then(() => console.log('async.js loaded'))
    }, 1000)
    ```

    ```js
    // async.js
    import './async.css';
    console.log('async.js content')
    ```

    For now the graph generated by above code will be like this:

    <img width="1461" alt="Screen Shot 2022-12-03 at 21 22 24" src="https://user-images.githubusercontent.com/42857895/205442932-ebfd5126-ef3d-4205-b5b5-434126ad46f7.png">

    The `ChunkGroup_async` will be a async chunk group of `ChunkGroup_index`, pushed at [turbopack-core/src/chunk/mod.rs#L462](https://github.com/vercel/turbo/blob/e1a9bcb94d439856982fd7edb522ba3122699f2d/crates/turbopack-core/src/chunk/mod.rs#L462), and it will have a reference between `ChunkGroup_index` and `ChunkGroup_async`, but `ChunkGroup_async` will also be a chunk group of `ChunkGroup_async-manifest-chunk` created at [turbopack-ecmascript/src/chunk/loader.rs#L165](https://github.com/vercel/turbo/blob/e1a9bcb94d439856982fd7edb522ba3122699f2d/crates/turbopack-ecmascript/src/chunk/loader.rs#L165), and will have a reference between `ChunkGroup_async-manifest-chunk` and `ChunkGroup_async`.

    This leads to when the browser request '/_a8a837.js', turbopack will compile chunks in `ChunkGroup_index` ('/_a8a837.js'), `ChunkGroup_async-manifest-chunk` ('/src_async.js_manifest-chunk.js'), and also chunks in `ChunkGroup_async` ('/src_async.js', '/src_async.css'), because of the reference between `ChunkGroup_index` and `ChunkGroup_async`.

    But the expected behavior is only compile chunks in `ChunkGroup_index` and `ChunkGroup_async-manifest-chunk`, so this PR deleted the reference between `ChunkGroup_index` and `ChunkGroup_async`, makes the graph be like this:

    <img width="1461" alt="Screen Shot 2022-12-03 at 21 50 29" src="https://user-images.githubusercontent.com/42857895/205444165-7b266dce-9aa6-4829-b8dc-d2bf74642aff.png">

    And makes chunks in `ChunkGroup_async` to be compiled only when the browser request '/src_async.js_manifest-chunk.js'.

commit fd09f2e7cba7bcff030c1f10f31fc0155dd055fe
Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Date:   Sun Dec 4 03:26:37 2022 +0000

    chore(deps): update dependency @types/node to v18.11.10 (vercel/turbo#2928)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Thomas Knickman <tom.knickman@vercel.com>

commit 429e91eae5c313556fe8cb0bde87ab521e28d7cf
Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Date:   Sat Dec 3 22:21:26 2022 -0500

    chore(deps): update dependency @babel/core to v7.20.5 (vercel/turbo#2919)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

commit c2d5a07dc58a57434cf2aed00a1ce428215f585e
Author: Tobias Koppers <tobias.koppers@googlemail.com>
Date:   Sat Dec 3 22:11:10 2022 +0100

    update chromiumoxide (vercel/turbo#2916)

    updating in hope that this fixes the random errors in test runs

commit e1a9bcb94d439856982fd7edb522ba3122699f2d
Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Date:   Sat Dec 3 08:54:50 2022 +0000

    chore(deps): update rust crate futures to 0.3.25 (vercel/turbo#2915)

    [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

    This PR contains the following updates:

    | Package | Type | Update | Change |
    |---|---|---|---|
    | [futures](https://rust-lang.github.io/futures-rs) ([source](https://togithub.com/rust-lang/futures-rs)) | dev-dependencies | patch | `0.3.21` -> `0.3.25` |
    | [futures](https://rust-lang.github.io/futures-rs) ([source](https://togithub.com/rust-lang/futures-rs)) | dependencies | patch | `0.3.21` -> `0.3.25` |
    | [futures](https://rust-lang.github.io/futures-rs) ([source](https://togithub.com/rust-lang/futures-rs)) | dependencies | patch | `0.3.24` -> `0.3.25` |

    ---

    ### ⚠ Dependency Lookup Warnings ⚠

    Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

    ---

    ### Release Notes

    <details>
    <summary>rust-lang/futures-rs</summary>

    ### [`v0.3.25`](https://togithub.com/rust-lang/futures-rs/blob/HEAD/CHANGELOG.md#&vercel/turbo#8203;0325---2022-10-20)

    [Compare Source](https://togithub.com/rust-lang/futures-rs/compare/0.3.24...0.3.25)

    -   Fix soundness issue in `join!` and `try_join!` macros ([#&vercel/turbo#8203;2649](https://togithub.com/rust-lang/futures-rs/issues/2649))
    -   Implement `Clone` for `sink::Drain` ([#&vercel/turbo#8203;2650](https://togithub.com/rust-lang/futures-rs/issues/2650))

    ### [`v0.3.24`](https://togithub.com/rust-lang/futures-rs/blob/HEAD/CHANGELOG.md#&vercel/turbo#8203;0324---2022-08-29)

    [Compare Source](https://togithub.com/rust-lang/futures-rs/compare/0.3.23...0.3.24)

    -   Fix incorrect termination of `select_with_strategy` streams ([#&vercel/turbo#8203;2635](https://togithub.com/rust-lang/futures-rs/issues/2635))

    ### [`v0.3.23`](https://togithub.com/rust-lang/futures-rs/blob/HEAD/CHANGELOG.md#&vercel/turbo#8203;0323---2022-08-14)

    [Compare Source](https://togithub.com/rust-lang/futures-rs/compare/0.3.22...0.3.23)

    -   Work around MSRV increase due to a cargo bug.

    ### [`v0.3.22`](https://togithub.com/rust-lang/futures-rs/blob/HEAD/CHANGELOG.md#&vercel/turbo#8203;0322---2022-08-14)

    [Compare Source](https://togithub.com/rust-lang/futures-rs/compare/0.3.21...0.3.22)

    -   Fix `Sync` impl of `BiLockGuard` ([#&vercel/turbo#8203;2570](https://togithub.com/rust-lang/futures-rs/issues/2570))
    -   Fix partial iteration in `FuturesUnordered` ([#&vercel/turbo#8203;2574](https://togithub.com/rust-lang/futures-rs/issues/2574))
    -   Fix false detection of inner panics in `Shared` ([#&vercel/turbo#8203;2576](https://togithub.com/rust-lang/futures-rs/issues/2576))
    -   Add `Mutex::lock_owned` and `Mutex::try_lock_owned` ([#&vercel/turbo#8203;2571](https://togithub.com/rust-lang/futures-rs/issues/2571))
    -   Add `io::copy_buf_abortable` ([#&vercel/turbo#8203;2507](https://togithub.com/rust-lang/futures-rs/issues/2507))
    -   Remove `Unpin` bound from `TryStreamExt::into_async_read` ([#&vercel/turbo#8203;2599](https://togithub.com/rust-lang/futures-rs/issues/2599))
    -   Make `run_until_stalled` handle self-waking futures ([#&vercel/turbo#8203;2593](https://togithub.com/rust-lang/futures-rs/issues/2593))
    -   Use `FuturesOrdered` in `try_join_all` ([#&vercel/turbo#8203;2556](https://togithub.com/rust-lang/futures-rs/issues/2556))
    -   Fix orderings in `LocalPool` waker ([#&vercel/turbo#8203;2608](https://togithub.com/rust-lang/futures-rs/issues/2608))
    -   Fix `stream::Chunk` adapters size hints ([#&vercel/turbo#8203;2611](https://togithub.com/rust-lang/futures-rs/issues/2611))
    -   Add `push_front` and `push_back` to `FuturesOrdered` ([#&vercel/turbo#8203;2591](https://togithub.com/rust-lang/futures-rs/issues/2591))
    -   Deprecate `FuturesOrdered::push` in favor of `FuturesOrdered::push_back` ([#&vercel/turbo#8203;2591](https://togithub.com/rust-lang/futures-rs/issues/2591))
    -   Performance improvements ([#&vercel/turbo#8203;2583](https://togithub.com/rust-lang/futures-rs/issues/2583), [#&vercel/turbo#8203;2626](https://togithub.com/rust-lang/futures-rs/issues/2626))
    -   Documentation improvements ([#&vercel/turbo#8203;2579](https://togithub.com/rust-lang/futures-rs/issues/2579), [#&vercel/turbo#8203;2604](https://togithub.com/rust-lang/futures-rs/issues/2604), [#&vercel/turbo#8203;2613](https://togithub.com/rust-lang/futures-rs/issues/2613))

    </details>

    ---

    ### Configuration

    📅 **Schedule**: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

    🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

    ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 **Ignore**: Close this PR and you won't be reminded about these updates again.

    ---

     - [ ] If you want to rebase/retry this PR, check this box

    ---

    This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/vercel/turbo).

commit 93222f2b22d43bd9c1d917350f810e5398ca9d49
Author: Anthony Shew <anthony.shew@vercel.com>
Date:   Fri Dec 2 16:36:55 2022 -0800

    feat(docs): document topology outside of a task (vercel/turbo#2879)

    * Docs for topology outside of a task

    Documentation for behavior in vercel/turbo#2855!

    * Minor cleanup.

    * Some copy updates and add image.

    Co-authored-by: Thomas Knickman <tom.knickman@vercel.com>

commit f8aaf81cb7c833f672001eb36d30d700e1cf6cc9
Author: Will Binns-Smith <wbinnssmith@gmail.com>
Date:   Fri Dec 2 16:32:35 2022 -0800

    Link to Turbopack's architecture.md from CONTRIBUTING.md (vercel/turbo#2913)

commit 07231701892cbca7b73e35bfb490f2514770628e
Author: Thomas Knickman <tom.knickman@vercel.com>
Date:   Fri Dec 2 16:40:08 2022 -0500

    feat(docs): add github (vercel/turbo#2912)

commit c69298c4a31516129bb62263f163a1da9c5614da
Author: OJ Kwon <1210596+kwonoj@users.noreply.github.com>
Date:   Fri Dec 2 11:58:55 2022 -0800

    build(cargo): update swc_core, dependencies to resolve circular deps (vercel/turbo#2869)

    * build(cargo): bump up swc_core

    * build(cargo): unpin indexmap

    * build(cargo): update dependencies

    * style(cargo): adjust format

commit 6965cb81ef5693b3e7a23e6a999be04d6590fad5
Author: Leah <github.leah@hrmny.sh>
Date:   Fri Dec 2 19:42:05 2022 +0100

    set correct cwd for server renderer (vercel/turbo#2886)

commit 934567015bc99eb8aa80311623e52ea924cbc424
Author: Leah <github.leah@hrmny.sh>
Date:   Fri Dec 2 18:27:02 2022 +0100

    fix dynamic paths (vercel/turbo#2884)

commit eead9063968a3b8571e3ba2c7a897522f890e2fc
Author: Nathan Hammond <nathan.hammond@vercel.com>
Date:   Fri Dec 2 16:09:08 2022 +0800

    Fix the missing links. (vercel/turbo#2707)

    This PR does three things:
    1. Prevents double redirects by setting the correct destination the first time.
    2. Redirects URLs accidentally recreated in the new scope. 🤦‍♂️
    3. Removes a catch-all to trigger any additional missing links to appear.

    Changes are easy to review commit-by-commit.

commit b8c0c3c74636fd4b0586951011919bc05e1f651d
Author: Nathan Hammond <nathan.hammond@vercel.com>
Date:   Fri Dec 2 14:37:03 2022 +0800

    Update lint-staged behavior. (vercel/turbo#2904)

    Before vercel/turbo#2859:
    `eslint --quiet --fix`

    After vercel/turbo#2859:
    `pnpm run lint --quiet --fix --`
    =>
    `eslint . --ext js,jsx,ts,tsx --quiet --fix --`

    After this:
    `eslint --ext js,jsx,ts,tsx --quiet --fix --`

    Removes the sneaky `.`.

commit 336ea22098ff8825e83baa2561d8ec0acf5b52af
Author: Nathan Hammond <nathan.hammond@vercel.com>
Date:   Fri Dec 2 08:33:21 2022 +0800

    Add additional detailed warning message if no tasks were run. (vercel/turbo#2778)

    This is a quality of life improvement output log so that you don't have to tease it out from the overall run summary and the situation is more-apparent.

commit dcb1ab33d1f9571177b9db51e3e0cbbbe8e021e1
Author: Leah <github.leah@hrmny.sh>
Date:   Thu Dec 1 21:02:33 2022 +0100

    simplify `next-binding` (vercel/turbo#2899)

commit 22c1440283ed4dfd1e310210108244c4c12d4c56
Author: Justin Ridgewell <justin@ridgewell.name>
Date:   Thu Dec 1 13:55:15 2022 -0500

    Implement import.meta (vercel/turbo#2816)

    I chose to have the `import.meta.url` to have the relative project path on disk.

    Webpack makes it the absolute system path, but that would make the JS output system dependent and I didn't like that. Vite doesn't bundle and uses the browser's behavior, which is the dev server path.

    I'm splitting this from the in-progress PR to implement `new URL(…, import.meta.url)` support. That requires a bunch of changes to the analysis code and a new FS content source, so it's taking longer to ship.

    Fixes WEB-137.

commit 75a7d1ea450cdaa629920464b509f3098997ae06
Author: Thomas Knickman <tom.knickman@vercel.com>
Date:   Thu Dec 1 11:40:15 2022 -0500

    fix(examples): cra pnpm fix (vercel/turbo#2897)

* Merged main

* Reverting changes that snuck in

* Fixing tests

* Final fixes for tests

* Moving shim to crates/turborepo

* More refactoring

* First pass at splitting up shim and cli

* Fixing tests

* Added detection for help flag so users can get help outside of a valid repo

* Update crates/turborepo-lib/src/shim.rs

Co-authored-by: Chris Olszewski <chrisdolszewski@gmail.com>

* Update crates/turborepo/Cargo.toml

Co-authored-by: Chris Olszewski <chrisdolszewski@gmail.com>

* PR feedback and test fixing

* Set process's cwd

* Have to do inference even with TURBO_BINARY_PATH

* Comments

* PR feedback

* Moved single_package back to RunArgs

* Removed print

* Fixing bugs

* Fixing rust tests

* fixing bug with verbosity and Go tests

* add local turbo version checking

* remove ffi inclusion

* Fixed integration tests

* Linting fixes

* Integrated local_turbo_supports_skip_shim

* Fixed bug with cwd and restored yarn.lock

* Okay back to setting current_dir

* Fixed bug with canonicalization

* Removed print
starting

Co-authored-by: Chris Olszewski <chrisdolszewski@gmail.com>
Co-authored-by: Florentin / 珞辰 <ecklf@icloud.com>
Co-authored-by: Chris Olszewski <chris.olszewski@vercel.com>
Co-authored-by: Thomas Knickman <tom.knickman@vercel.com>
Co-authored-by: Matt Pocock <mattpocockvoice@gmail.com>
Co-authored-by: Mehul Kar <mehul.kar@vercel.com>
Co-authored-by: Yota Hada <hadayota33@gmail.com>
Co-authored-by: Justin Ridgewell <justin@ridgewell.name>

Easy clippy improvements via `clippy --fix`.

Implements `new URL('./path', import.meta.url)`, so that the referenced file acts as a static output file, and transforms the URL into to point to that file in the graph.

This is, well, complicated. As you'll see in the comments, we have an "inert" asset that acts as a placeholder until the module chunking algorithm gives us access to a `ChunkingContextVc`. It's unfortunately not available when we're doing the file parsing, but we can insert a reference to that inert asset. That inert asset will eventually create a `UrlAssetChunk` instance, and with that we can finally generate the correct output path for the URL referenced file.

We actually discussed whether this could use a `StaticAsset`/`StaticModuleAsset` (a `StaticAsset` can be inserted at parse time), but it turns out that won't give us the necessary control to generate the final `URL` instance. A `StaticModuleAsset` always outputs an absolute path as it's default export, and that just won't work when we're trying to reference the file in node SSR.

Fixes WEB-142.
Pending WEB-279 for full node SSR support.

Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>

…rbo#2994)

Implement / fixes WEB-306.

We can't rely on default tls backend for reqwest and hope to work with
every target platform we support, due to several constraints. Some
target cannot use -sys (openssl-sys), and some can't build rustls due to
trasnsitive dep support issue.

PR creates explicit opt-in features for those and let upstream
application can specify what they need. `next-dev` currently sets
`native-tls` as default for the general dev workflow conveniences, but
that doesn't mean we promote it as default feature set - next-swc, or
other like standalone turbopack will configure features by themselves
when build binaries for their own.

Implements / fix WEB-86. This PR is an initial attempt to support mdx
natively inside of turbopack.

It uses mdxrs (https://github.com/wooorm/mdxjs-rs) internally to interop
- compile - mdx inputs into renderable ecma outputs. PR creates a new
type of asset `MDXAsset`, and then let its extension (`.mdx`) can be
consumed by turbopack.

Since mdx is a variant of ecma asset to be rendered, it requires to
perform all of the ecma transforms in the current running turbopack
session. But since its AST is not compatible to plain swc (or ecma), it
also cannot be passed into existing ecmaassets. MDXAsset does interop
for those, by creating a virtualasset for the ecma once mdx is compiled
into plain ecma. This might not be feasible appoarch and requires
different way to chain asset types, something I'd like to address in
this PR. I guess this will be needed for other types of assets in a long
run - where input is not an ecma but requires ecma transforms (i.e vue,
ng templates).

Fixes WEB-259

This should address the known cases of flakiness in the next-dev
integration test suite. Most notably, it wraps the call to
`browser.new_page`, which not only opens a new tab, it also navigates to
the destination and waits for it to load. It also:

* Migrates test code to `anyhow::Result`, and adds `context` to the
`new_page` call should it fail again.
* Mitigates flakiness resulting from browser-side Jest timeouts by
moving the circular correctness test to a new directory called
`__flakey__`. These tests aren't run at all -- unfortunatley it's not
possible to customize Jest's timeout with this particular version of
`jest-circus-browser`. WEB-319 tracks updating this dependency, which
hasn't been maintained in a while, unlike `jest-circus` itself.

Test Plan:
* [x] Run the Rust test suite in CI until confident there are no
intermittent failures.

In order to serve source maps with HMR updates, we (used to) reference a source map asset for every chunk item using the items version hash (see vercel/turbo#2464 and vercel/turbo#2474 for the headaches this can cause).

This update changes that, so that a chunk becomes responsible for giving access to one of its item's source map. We already have the `GenerateSourceMap` trait which assembles the chunk's `Sectioned` source map from all chunk items, so why not just allow access to an individual section? Coupled with a `ContentSource` that can retrieve the chunk, we can then provide access to that chunk's current item source maps per request.

Load next.config.js via turbopack-node

Closes WEB-158

Co-authored-by: Justin Ridgewell <justin@ridgewell.name>
Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>

Re: code review nits from vercel/turbo#2955

HMR is handled via an `eval(newCode)`, and that eval will inherit the filepath of the currently running file (in our case, the chunk file that contains the runtime code). To properly trace, we need to know both the chunk and the item ids, so we trace via the correct item's source map.

Thankfully, we can use the (underspecified) [`//# sourceUrl` ](https://learn.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/javascript/source-maps#use--sourceurl-to-name-evaluated-files-in-the-sources-tool) meta comment to name the file we're currently evaluating. That'll get used as the stack frame's file. We can then encode the chunk path and item id into the filename, and let next's stack tracing code handle the rest.

This also fixes an off-by-one on the column. Source maps are 0-based, but the line/column of a file as displayed in an editor or dev tools are 1-based.

and `__NEXT_STRICT_MODE_APP`

Seems vercel/turbo#2878 removed this accidentally

This adds the ability to add Source transforms on assets, which modify
the source code of an asset before parsing.

This adds postcss via node.js as first source transform.

Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>

Re: vercel/turbo#3065

It also fixes the gnarly stack trace error whenever the node code throws, but it doesn't look very pretty. Not sure how to handle it:

<img width="1280" alt="Screen Shot 2022-12-19 at 3 46 56 PM" src="https://user-images.githubusercontent.com/112982/208519095-ec7ad539-5c23-4b95-bcc1-71ba30381e60.png">

Fixes WEB-341

This incorporates a digest of the font request into the name of the
font-family defined in the stylesheet, used in the css class, and
returned to the JavaScript importer. This makes font-family names
returned from `@next/font/google` in stylesheets unguessable.

Note that this implementation uses 8-character long hex digests compared
to the 6-character version in Next.js+webpack.

Test Plan: imported Open Sans as a symbol, verified that stylesheet is
updated to reference both `@font-face` definitions and the css class
rules with `font-family: '__Open_Sans_3b020fa1';`. Verified that
exported js object `style.fontFamily` references the same.

A follow up to vercel/turbo#2944, which incorrectly rewrote the `new URL("…", import.meta.url)` to `new URL("…", location.origin)` during server rendering (which obviously doesn't have a `location` object).

This PR accomplishes 2 things:
- Splits dev server address binding from setting up the handler function
  - This is necessary so that we can determine the bound server address during devs retry attempts.
- Propagates the server address through the `ExecutionEnvironment` to the `UrlAssetReference`

I chose to pipe the server address through the `ExecutionEnvironment` instead of the `EnvironmentIntention`, because I don't fully understand the differences between them. It seems like we want it in the intention for the types of rendering, but a server address is really tied to the node process, so I don't know.

Fixes WEB-318

add counting seconds when something is happening. Only starts to show
when compilation takes more than 1s

Co-authored-by: Alex Kirszenberg <alex.kirszenberg@vercel.com>

pass the dependencies reported by postcss to turbo-tasks-fs. We don't
have a good mechanism to track dependencies back-timed, so we start
watching some as soon we know about the dependencies (after postcss
compilation)

tailwind reports dependencies as directory + glob, so our globbing need
some improvements to handle these globs reported by tailwind.

e.g. tailwind will rerun when any file changed from the tailwind config
`content` globs.

fixes WEB-356

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

Any `404.js` page would inject a `[...]` path into the server generation. The problem comes from the `pathname_for_path` function, which will extract the extension from that path. In this case, it leads to a basename of `[...` and an extension of `]`, breaking the `regular_expression_for_path` dynamic route parser.

Unfortunately, our integration tests timeout when I try to write a basic test case for this, so it's not possible to test at the moment. I've manually verified.

Fixes WEB-214

…#3110)

Co-authored-by: Alex Kirszenberg <alex.kirszenberg@vercel.com>

…ercel/turbo#3108)

Fixes WEB-43
Closes vercel/turbo#3104

* add GlobalError export to layout entry (see
#44066)
* update app manifest for CSS (see
#44168)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

#3021
[removed](https://github.com/vercel/turbo/pull/3021/files#diff-c6405fb94033af4296b1f72626fb990aaf76f645b6ed0f7812c56fcad719cf0eL304-L306)
1 level of error wrapping, and the unwrapping code was not updated to
match.

- Adds `details` to `SourceMapContentSource`
- Fixes `ty` of `SourceMapContentSource`
- Adds default `children` trait method that returns empty children

…rbo#3118)

fixes weird typescript errors caused by types being referenced by .ts
files

- The 10th attempt used to day "trying again" and then didn't try again because the iterator ended…
- Swaps a nested `.map() == Some(bool)` for a `and_then`
- Extracts into a helper function so code can early return without an `Option<Result>` wrapper.

…urbo#3124)

Currently when an individual `ContentSource` inside a `CombinedContentSource` requests additional vary data, the combined source will treat that source as the winner of the query. But, sometimes the vary data is necessary to determine that the content is not found by this source. And if that's the case, we'll hit a 404 when we should actually keep iterating.

This is exactly the case we're going to hit with redirect/rewrites. Redirects need to be the very first content source, and I also need query/header/cookie/hostname data in order to determine if a redirect applies. Without this, **every** request becomes a 404.

…el/turbo#2968)

## The original transform

The original behavior of the Next SSG transform is to remove `getServerSideProps`, `getStaticProps`, and `getStaticPaths` from Next.js page files so they can be bundled for the client. This is what enables the following code to work properly without advanced tree shaking:

```jsx
import db from "db";
import PostCounter from 

export default function Home(props) {
  return <>{props.posts.length} post(s)</>;
}

const postsPromise = db.getPosts();

export async function getStaticProps() {
  return {
    props: {
      posts: await postsPromise,
    },
  };
}
```

The transform is able to remove both `getStaticProps` and all its exclusive, transitive dependencies, so this is what the client would see:

```jsx
import PostCounter from "components/PostCounter";
export var __N_SSG = true;
export default function Home(props) {
    return __jsx(PostCounter, {
        count: props.posts.length
    });
}
```

## Adding the inverse operation

However, to support proper HMR for these data exports, we need to be able to execute somewhat of an inverse operation: remove the default component export, but preserve all the rest. This allows Turbopack to bundle server-side only declarations, only re-rendering when one of these changes, instead of re-rendering on any server-side and client-side change.

From our module above, the updated transform is now also able to generate the following:

```jsx
import db from "db";
const postsPromise = db.getPosts();
export async function getStaticProps() {
    return {
        props: {
            posts: await postsPromise
        }
    };
}
```

As you can see, this module is no longer importing the `PostCounter`, which means re-rendering will not invalidate when that counter changes. However, if the "db" module changes, we will still be able to detect a change and re-render.

## Other notes

* I renamed the transform from "next_ssg" to "next_transform_strip_page_exports". It's much more verbose, but hopefully also much clearer about what it does at a glance.
* I took the liberty to clean up and comment some parts of the transform to make it more easily understandable (at least for someone like me, who hasn't written a lot of SWC code). I also fixed a few bugs and edge cases.
* I brought over the tests from the transform in the Next.js and added a couple of them.
* For now, only the `StripDataExports` filter is used. A future PR will build on this and @ForsakenHarmony's vercel/turbo#2949 PR to actually implement SSR/SSG HMR. 

## Reviewing guide

1. The crux of the change is the move (and refactor) of the next ssg transform from https://github.com/vercel/turbo/pull/2968/files#diff-133d73657647ed793ca4782a73552650b32ad565094b1e0faf452ad58705499b to https://github.com/vercel/turbo/pull/2968/files#diff-d6442fa6af9b66e581f062739dd6de2419f5e8f6f3d97cfa63518c72b0a9ee3e.
2. I also added the [errors.rs](https://github.com/vercel/turbo/pull/2968/files#diff-0f308375da4179c0ea5a0fcbd99593b56d6020cd7dec1694ed08f392f1637c09) and [fixture.rs](https://github.com/vercel/turbo/pull/2968/files#diff-6e23f34483fc17a27dfc630edb455ea95e28d5cb350468c2ba01384fbc3c116a) tests. I adapted fixture.rs to execute on the two transform filters: data exports and default export.
3. Most of the tests in `tests/` are copied from https://github.com/vercel/next.js/tree/canary/packages/next-swc/crates/core/tests. The changes I made are:
  i. https://github.com/vercel/turbo/pull/2968/files#diff-774abee6a1bf139c9ce55e226bf15b52e56ea091170ee5d6295c191fd8d793c7: made this one symmetric for both strip data and strip default transforms.
  ii. https://github.com/vercel/turbo/pull/2968/files#diff-4792266a264dc67da93748d2c6522917f860527a689891bd5f8f4add9841e7f6 wasn't supported before AFAIK.
  iii. https://github.com/vercel/turbo/pull/2968/files#diff-a3b12adbce1dec40f39ff8af13ffecbe7f6963e21bc402cef6332ecf5018877e similar to i.

Based on vercel/turbo#2968 

This builds upon vercel/turbo#2968 and @ForsakenHarmony's work on data routes to
enable page data HMR.

Page data HMR is a bit more clever than it is in Next.js as we won't
re-render a Node.js result for each page file update. Instead, thanks to
the `StripPageDefaultExport` transform, there are three versions of the
page chunks:
* client-side (strips page data exports);
* server-side (full);
* data server-side (strips page default export).

Instead of subscribing to the full server-side result, on hydration, the
client-side page separately subscribes to:
* client-side updates (already the case);
* data server-side updates (new).

This means that updating something that only affects the page component
will only cause a client-side update and **no Node.js re-rendering**,
while updating something that only affects the data will only cause a
server-side update.

~~I'm marking this as a draft for now as there are still a few areas to
test/investigate:~~
- [x] When something that is used in both the default page export and
data exports is changed, this will cause *two* HMR updates: one data
update, and one client-side chunk update. **The same case breaks in
Next.js, where we will receive a client-side update, but no server-side
update, ending up with an incorrect result.**
- [x] Differences between `getStaticProps/getServerSideProps`, as well
as `getInitialProps` (need to talk with @timneutkens about this) (see
#44523)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

This is a straightforward chore PR to move next_client and next_server modules
around, in order to make navigation and imports more predictable between them.

I'm also planning to introduce a next_shared::context in a further PR, hence the
changes.

…rbo#3220)

Addresses an issue currently affecting non-variable fonts in which
`next-dev` errors for non-variable Google fonts. This issue can be
replicated by using `next dev --turbo` and using a Google font that
isn't variable, like Hind.

The problem is resolved by unwrapping axes only if the font is variable.

Relevant issue: #44282

Co-authored-by: Will Binns-Smith <wbinnssmith@gmail.com>

Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action

Co-authored-by: Will Binns-Smith <755844+wbinnssmith@users.noreply.github.com>

I verified that CI works with this change.


https://github.com/kdy1/turbo-windows-path-length/actions/runs/3889566103/jobs/6638025437

---

x-ref: #44760

x-ref:
https://github.com/vercel/next.js/actions/runs/3888528533/jobs/6635975573
x-ref:
https://github.com/vercel/next.js/actions/runs/3888528533/jobs/6635975680
x-ref:
https://github.com/vercel/next.js/actions/runs/3888528533/jobs/6635976658

…3193)

This PR separates Turbopack's `runtime.js` into two:

- the Browser/DOM implementation, which uses `<script>` and `<link>`
tags for dynamically loading chunks;
- the Node.js/CommonJS implementation, which uses `require` instead.

~~The two runtimes share a lot of code, but I'm not sure what's the best
approach for sharing this logic, or even if we should, so for now they
are two separate entities.~~

The shared code between the two runtimes is now in a separate file to
avoid duplication.

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

…o#3291)

add the minimum to run a simple raw-loader (see test case)

* add `experimental.turbopackWebpackLoaders` to next.config.js
* key is extension like `".mdx"`, value is an array of loaders like
`["mdx-loader"]`

…ercel/turbo#3297)

The `processed_assets` `IndexSet` was performing deduplication on the `AssetVc`, which is the same between static (`import ... from "foo"`) and dynamic (`import("foo")`) imports of the same specifier. But, the _reference_ to those assets is different, and generates different chunking semantics. In order for both to succeed, we need to process both assets.

Coupled with vercel/turbo#3193's ability to load chunks on the server side, this fixes fixes WEB-381.

…turbo#3298)

Fixes WEB-416.

This implements loading an alias map set as `experimental.resolveAlias`
in `next.config.js`.

Test Plan: Added an integration test.

This PR adds the next/dynamic SWC transform to the repo. This is copied
over from the implementation in
[](https://github.com/vercel/next.js/blob/f70a6bfb8635929feeecc92413da1fb2b651a18d/packages/next-swc/crates/core/src/next_dynamic.rs),
with an additional mode for Turbopack.

For now, it applies it to all sources files (excluding node_modules, but
including embedded modules).

I've refactored the Next transforms logic to make it more easily
extendable in the future, and avoid creating more Vcs than absolutely
necessary.

This PR is the last item in the list of what's needed to support
next/dynamic in development.

This adds two basic tests for next/dynamic:
* one ensures that SSR supports dynamic components;
* the other ensures that SSR doesn't run when `ssr: false`.

since they don't have exactly the same API

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

#44668 refactored Next's use of `AsyncLocalStorage`, and installs a "polyfill" of the API by patching the node import onto `globalThis.` Importantly, it's then used in the module scope during imports, so we need to install the polyfill early in the app rendering startup.

Fixes vercel/turbo#3319

This:

* Implements a basic http server to mock returning a stylesheet from the Google Fonts API (**Note**: This importantly does *not* mock returning the font resources themselves, which are currently loaded by the browser. We should implement something to do this when we implement caching arbitrary http resources traced from `url()` and this is no longer loaded by the test browser)
* Adds an integration test that asserts the basic shape of the JS object returned by font functions
* ~Adds an integration test that asserts the browser correctly loads a font for the ascii unicode range, along with the appropriate `font-display`, variant, etc.~ Unfortunately `document.fonts` is not reliable with different font-display loading patterns as any of them can fall back.

As noted, this does not mock responses from Google for the font resources themselves, which are currently loaded by the test browser. This means that we'll be dependent on this external service for passing integration tests until we implement caching of `url()`s in Turbopack. We should monitor the reliability of this test.

…inspect-brk (vercel/turbo#3385)

This implements a debug mode for spawning Node processes across multiple surfaces including `evaluate` and `get_renderer_pool`.

It:

* automatically limits concurrency to 1 process per pool
* passes `--inspect-brk` to spawned Node process
* sets the timeout to effectively-infinite duration

Test Plan: set the value to true for the call to `get_renderer_pool` in render_static.rs and attached to a debuggable server renderer process.

…copies (vercel/turbo#3386)

Fixes WEB-412.

Previously, references to styled-jsx inserted by the swc transform would be bundled, which duplicated the copy required by next, which is external. This marks the dependency is to be resolved as external always.

Test Plan: Verified in a small app that `<style jsx>` nodes result in a server-rendered response with the appropriate `<style>` tag in the head.

fixes WEB-265
fixes WEB-268
fixes WEB-4
fixes WEB-359

vercel/turbo#3324)

… client/server only

…es (vercel/turbo#3288)

I verified that the crate is rebuilt if I make a change of inputs.

Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>

This updates our `mdxjs` dependency to the tip of
wooorm/mdxjs-rs#11, so that we can update it's
`swc_core` dependency (it conflicts with ours).

It also updates the `testing` crate to update it's `swc_common`
dependency (also conflicting with ours), and makes it a workspace
dependency.

Our `pageData` HMR process treated an undefined response as an error condition, but if the page doesn't have a `getXyzProps` exported method, then this is the default response. This prevented us from having any pages without page props.

The new code just sends down an empty object, which seems to work for establishing the connection. HMR updates are sent down (and seem to trigger restarts, at least from what I tested with `getStaticProps`).

Fixes WEB-445

…ercel/turbo#3334)

fixes WEB-141

This changes the ContentSource API.

Before a ContentSource returned a tuple of specificity and content.
Now it returns a tuple of specificity and a get_content function.

The old way made it very inefficient to combine multiple ContentSource.
All combined ContentSources were ask before, all returned specificity
and content, and they are ordered after that. That required to compute
all contents, even if it is not really used after ordering.

Now we order specificity and a get_content function and only compute the
content (by calling get_content) with the final result.

It also changes how data needs are expressed in the `get_content`
function. Instead of asking it over and over again with more data, it
statically returns the needed data with `vary` and the `get` function is
only called with that data. This is technically more limited than the
old way, but one can workaround that if needed. But practically we
probably never need that. On the other hand it improves the number of
function calls, since the `vary` method is only called once and the
`get` only once per request. Before data needs required at least 2 `get`
calls per request.

In addition to the fix, I've extracted the path regex/params matching logic from `turbopack-node` to `next-core`. `turbopack-node` now only declares a value trait which `next-core` implements.

Automated changes by
[create-pull-request](https://github.com/peter-evans/create-pull-request)
GitHub action

Co-authored-by: wbinnssmith <wbinnssmith@users.noreply.github.com>

This adds support for metadata in pages and layouts.

Full metadata support also needs support for implicit metadata with
files named `icon.ico` etc.

This PR also improves the test suite and adds a basic test case for app
dir support

…rbo#3396)

Automated changes by
[create-pull-request](https://github.com/peter-evans/create-pull-request)
GitHub action

Co-authored-by: wbinnssmith <wbinnssmith@users.noreply.github.com>

This implements routing by using a-yet-to-be-implemented API exposed by
Next.js. The API follows something similar to:

```typescript
type MakeResolver = (config: NextConfig) => Resolver;
type Resolver = (IncomingMessage, ServerResponse) => Promise<void> | void;

import { makeResolver } from "next/dist/...";
const resolver  = makeResolver(nextConfig as object);

// Later, once we have a request we'd like to route:
// We don't care what the promise resolved to, we just want it to settle.
await resolver(req, res);
```

The resolver can do 1 of 3 things with this:
1. ~~Return a redirect response~~ Removed
2. Return a rewrite response
3. Stream a middleware response

> ~~1. Return a redirect response~~

<details>

First, ensure a `x-nextjs-route-result: 1` header is present on the
response. Then return a JSON encoded body:

```typescript
{
  url: string,
  statusCode: u16,
  headers: Record<string, string>
  isRedirect: true
}
```

The Rust server will then respond with a redirect using to the
appropriate location.

</details>

> 2. Return a rewrite response

First, ensure a `x-nextjs-route-result: 1` header is present on the
response. Then return a JSON encoded body:

```typescript
{
  url: string,
  headers: Record<string, string>
}
```

The Rust server will use this updated URL to request content from our
handlers.

> 3. Stream a middleware response

Ensure `x-nextjs-route-result` header **is not present** on the
response. All headers will be sent back, and the body will be streamed
back to the browser.

- - -

TODO:
- ~~Do `headers` actually matter to a `redirect`~~ Yes?
- ~~Does `statusCode` actually matter to a `rewrite`?~~ No
- ~~We can't handle streaming body responses yet.~~ Mocked by buffering.

Fixes WEB-228

Co-authored-by: JJ Kasper <jj@jjsweb.site>

This completes a few review requests from vercel/turbo#3446.

…urbo#3505)

Fixes WEB-501

Fixes vercel/turbo#3139

This adds proper support for the [`variable`
property](https://nextjs.org/docs/api-reference/next/font#variable) when
constructing fonts. This results in:

* defining a selector in the css module for a classname defining the css
custom property (css variable), whose value is the font family
* adding a `variable` property to the resulting js object whose value is
the classname used in the selector above

Test Plan: Added an integration test.

Enables the anyhow backtrace feature to capture backtraces for errors
too when `RUST_BACKTRACE` is enabled.

When running in release mode compiling with
`CARGO_PROFILE_RELEASE_DEBUG=1` is recommended to get debug info into
the errors.

…ot found (vercel/turbo#3448)

This specifically supports the case where `getStaticProps.notFound =
true` or a matching route is not found, but not the case where
`getStaticPaths.fallback = false` and the route is not enumerated;

This separate case will be implemented in another PR.

This PR adds support for returning `redirect: { destination, permanent,
statusCode }` from `getStaticProps`.

The new error paths introduced in vercel/turbo#3448 both write their outputs to
`.next/server/pages/`, which conflicts with:
- The main pages source
- Each other

The infinite loop is very fun:
1. We need a `NodeJsPoolVc` to render pages
2. To get a `NodeJsPoolVc`, you need to write your files onto disk
    - So a pool is dependent on the contents of those files
3. When we render an error page, we need to write those files to disk
4. The error page shares the same file entrypoint as the main page
source

So, to render an error, we write the entrypoint, which is shared with
main source. This alone is pretty bad, because it will invalidate our
page source's node pool (and kill those processes). But, the loop is
triggered by a more subtle bug:

When we write a file, we read it to see if the contents have changed.
Writing creates a dependency on the read! So when the error page is
written to disk, it invalidated the read we preformed when we wrote the
main page. That invalidated the main page (and it's node pool), and so
we rendered again. That wrote the main page's code to disk, invalidating
the read of the error page performed when we wrote the error page. ♾️

(I'll be opening more PRs…)

The previous PR vercel/turbo#3499 only implemented support for `pages` directory.

The `app` directory previously had no validation at all, it's added with
this PR.

Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>

Next.js's integration test suite depends on these ids and data attributes to select against items in running test pages. This gets us passing some of those tests.

This addresses feedback from vercel/turbo#3505

…bo#3545)

Returning a 404 status code is required for the client-side router to
redirect to the error page.

…vercel/turbo#3437)

Fixes WEB-447.

Previously, generated classnames would include literal `/` characters,
which need escaping when generating selectors. While users should still
escape selectors, this avoids it for this case and makes generated code
easier to read. This format is also more aligned with what webpack-based
css modules generates.

This also removes the square character as a separator, since it breaks
words and makes double-clicking for selection more difficult.

Fixes WEB-525

This allows webpack loaders defined by `experimental.turbopackLoaders` in `next.config.js` to pass serializable options to loaders.

It expands `turbopackLoaders` to accept not just loader names for a given extension, but also `{loader: string, options: Object}`. These options are verified to be serializable and passed to `loader-runner` and exposed as `getOptions()` to the loader.

Test Plan: Added an integration test for basic options. Verified the serializable check by passing `class Foo {}; new Foo()` as an option value and verified the error was displayed.

#3437 wasn't up to date with main when it was merged.

Test Plan: CI

some packages expect `worker` or `browser` condition to work on edge
runtime

In Turbopack, as a consequence of our lazy compilation model, CSS chunks
can contain duplicate CSS chunk items. This can cause issues with
precedence. Take the following example:

Initial CSS chunk:
```css
/* ... */

/* chunk item A */
h1 {
  font-size: 2rem;
}

/* ... */

/* other chunk item */
h1 {
  font-size: 4rem;
}

/* ... */
```

Dynamic CSS chunk (loaded after the first page load completes)
```css
/* ... */

/* chunk item A */
h1 {
  font-size: 2rem;
}

/* ... */
```

In this example, when the page first loads, the following rule will be
applied:
```css
h1 {
  font-size: 4rem;
}
```

But as soon as the dynamic CSS chunk loads, the following rule will be
applied instead:
```css
h1 {
  font-size: 2rem;
}
```

However, from the order of rules in the initial load, we know that the
former should still apply.

We can remedy this particular issue by wrapping each CSS chunk item into
its own
[`@layer`](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer)
(thanks @sokra for the idea!). This ensures that when a CSS chunk item
is re-encountered at a later time, it is automatically de-duplicated
thanks to the inherent CSS layering algorithm.

This is not an issue in Next.js as we can't have duplicated CSS chunk
items.

Adds resolve plugins (currently only running `after_resolve`, could add
`resolve` later)

Had to fix `ResolveResult::merge_alternatives` because it merged two
external results into `Unresolvable`

This adds the turbo-tasks function name as `context` of all fatal errors
propagated from executing or reading turbo-tasks functions.

That should help in debugging fatal errors.

…/turbo#3597)

With the addition of the Next.js routing layer at the root of our
content sources, we need the update server to also be able to follow
Next.js rewrites, like the HTTP server.

This requires the following:
* Rewrites need to be able to indicate a source where to "resume" after
rewriting. Otherwise, we would enter an infinite loop of the Next.js
layer rewriting to the Next.js layer.
* The resolving logic from `process_request_with_content_source` needs
to be extracted into its own function, so it may be called both from the
HTTP server (which expects fully resolved `ReadRef`s) and the update
server (which needs a `VersionedContentVc`): this is where
`resolve_source_request` comes in.

Co-authored-by: Justin Ridgewell <justin@ridgewell.name>

Moves all next-dev integration test code into a parent `input/`
directory, like our snapshot tests. This prepares for introducing
`issues` snapshots to next-dev integration tests.

Test Plan: CI

Allows to skip unreachable code based on compile-time constant
conditions

e. g.

```
if (!process.turbopack) {
  require("will-not-be-processed");
}
```

* add if() and process.turbopack fixes WEB-491
* Removes unreachable code fixes WEB-498
* evaluate some logical operations `&&`, `||`, `??`, `!`
* fix arguments handling fixes WEB-529
* nested effects for function called with closures
* handle closures when array methods are used fixes WEB-538
* evaluates `process.turbopack` fixes WEB-496

It's difficult to test an app, if a single error blocks using the whole
page.

Therefore, error overlay should always be closeable.

…turbo#3619)

Similar to our `try_join` helper this adds a
`try_flat_map_recursive_join` helper, which allows to async expand a
tree structure into all nodes. It will call the async mapper function
concurrently to allow parallelism. It will handle circular and duplicate
references and return all nodes in a determinstic way (breath-first).

Adds support for `getStaticPaths` returning `{ fallback: false }` by
building out all static paths and checking whether the resolved path is
included in that list.

`buildStaticPaths` requires the `next.config.js` path, as well as other
config options such as locale. I created WEB-546 to track being able to
pass them to the handlers.

Automated changes by
[create-pull-request](https://github.com/peter-evans/create-pull-request)
GitHub action

Co-authored-by: wbinnssmith <wbinnssmith@users.noreply.github.com>

The node evaluation always renders with `type: "commonjs"` and `require()` calls, so we'll always import the CJS files. But here we're importing the ESM files. That means we have 2 distinct instances of `requestAsyncStorage` in our node instance, and they cannot properly communicate with the other.

Fixes WEB-543