new·Earn with mozg — 20% of every monthSend somebody here and take a fifth of every plan payment they make, for as long as they keep paying — not a bounty on the first invoice. Your handle is the link, the window is thirty days, and the commission lands on your balance the second they pay. Free to join: if you have signed in, you already have the link. mozg.sh/earnall news →
mozg.beta
Sign in

Next.js · API reference · all subjects

turbopack configuration

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

@next/swc-linux-arm64-musl package purpose

The @next/swc-linux-arm64-musl package is the linux-arm64-musl binary for @next/swc.

next-taskless crate purpose and constraints

The next-taskless crate provides utilities for Next.js written without dependency on turbo-tasks, allowing them to be shared with webpack and rspack codepaths. This crate must be compilable to WASM so it works in environments where no native bindings are available.

next-taskless file IO pattern requirements

Utilities in next-taskless should not perform file IO directly. Instead, they should accept files they depend on as arguments (preferred) or via async trait methods or callbacks (acceptable). The crate should follow 'sans-io' patterns where possible.

Running tests with Turbopack

To run the test suite using Turbopack, use the -turbo version of the npm script. For example: pnpm test-dev-turbo test/e2e/app-dir/app/

Running tests against both Turbopack and Webpack

To run a test against both Turbopack and Webpack, use Jest's --projects flag. For example: pnpm test-dev test/e2e/app-dir/app/ --projects jest.config.*

Give your agent this brain