Files
next.js/test/e2e/turbopack-worker-asset-prefix/turbopack-worker-asset-prefix.test.ts
eacb749030 chore: upgrade next-rspack to rspack 2.0 (#92222)
## Summary
- upgrade `@rspack/core` to `2.0.0-rc.0`
- sync the in-tree next rspack Rust binding/toolchain with newer rspack
releases
- align Next server runtime selection so `NEXT_RSPACK` uses the
turbo-like app runtime path
- include missing compiled `@next/react-refresh-utils` output in
`ncc-compiled`

## What is done
- `@next/rspack` Rust binding builds locally
- `packages/next` builds locally
- rspack-related tests are running and have been reduced to deeper
runtime compatibility failures

## Rspack test investigation
Latest checked CI run: `build-and-test` run `27129243230` at head
`484e7bf1b30655a9f94d0855b9e00774b4b38cd0`.

Confirmed Rspack / webpack parity gaps:
-
`test/e2e/edge-runtime-configurable-guards/edge-runtime-configurable-guards.test.ts`:
Rspack does not expose the webpack parser hooks used by
`MiddlewarePlugin`. The current Rspack path falls back to SWC analysis
in `finishModules`, which can report diagnostics but cannot apply the
parser-time transforms that wrap `eval` / `new Function`, track
`InnerGraph` usage for used vs unused dynamic code, or apply
`unstable_allowDynamic` with webpack parity. Dev therefore misses the
expected dynamic-code runtime warnings and also reports false
`process.cwd` Edge warnings from Next internals; prod fails
allowed/unused dynamic-code cases.
-
`test/development/middleware-overrides-node.js-api/middleware-overrides-node.js-api.test.ts`:
same parser-hook limitation. Webpack can observe that `process.cwd` is
overwritten before use, while the Rspack SWC fallback statically flags
`process.cwd` as an unsupported Edge Node API.
- `test/production/css-features/css-compilation.test.ts`: the CSS is
minified and prefixed as expected, but the Rspack lightningcss path
currently does not expose/control source map generation the way this
test expects, so emitted CSS has no `sourceMappingURL` comment or `.map`
file to assert.
- `test/e2e/app-dir/server-source-maps/server-source-maps.test.ts`:
invalid source maps are not handled with the same graceful diagnostic as
webpack/Node source-map handling. Rspack logs the raw `webpack-internal`
frame for the damaged map case instead of surfacing the expected
`Invalid source map. Only conformant source maps...` message with the
cause.
-
`test/e2e/app-dir/parallel-routes-revalidation/parallel-routes-revalidation.test.ts`:
raw CI output observed a dev-mode timeout waiting for `networkidle`
after refresh/back/forward lazy fetching. This was not the final
structured failure in the latest run, but it remains a Rspack dev parity
follow-up around router cache lazy fetches and network settling.
- `test/e2e/middleware-src/middleware-src.test.ts`: after the test adds
root middleware files, Rspack dev still lets `src/middleware`
participate; the expected behavior is that only the root middleware
runs.
- `test/e2e/env-config/env-config.test.ts`: changing `.env` logs `Reload
env:` but the client keeps the previous `NEXT_PUBLIC_` value, pointing
at an Rspack dev env invalidation/HMR gap.
-
`test/e2e/app-dir/use-cache-without-experimental-flag/use-cache-without-experimental-flag.test.ts`:
after enabling the `useCache` flag, the dev server does not finish
restarting, pointing at build-error recovery/restart parity.
-
`test/development/app-dir/server-navigation-error/server-navigation-error.test.ts`:
middleware navigation-error cases hit `ERR_CONNECTION_REFUSED`,
consistent with the Rspack dev server exiting or restarting unexpectedly
during those error flows.
- `test/e2e/opentelemetry/instrumentation/opentelemetry.test.ts`: the
custom-server dev process exits before the SDK handle is initialized,
then cleanup fails on `shutdown`; this needs follow-up in Rspack
dev/custom-server startup.
- `test/e2e/next-image-new/app-dir/app-dir.test.ts`: after toggling
image source, `onLoadingComplete` still reports the previous image
dimensions/source, pointing at an Rspack dev image/HMR or asset
invalidation parity issue.
- `test/e2e/node-cli-args/node-cli-args.test.ts`: on Node `20.19.x`,
`node --experimental-network-inspection` resolves instead of rejecting.
This looks like a Node-version behavior change rather than an Rspack
compiler issue.

Not attributed to this Rspack upgrade:
-
`test/e2e/app-dir/instant-navigation-testing-api/instant-navigation-testing-api.test.ts`
was marked by `scripts/pr-status.js` as a known flaky test across
branches.
-
`test/production/app-dir/build-output-prerender/build-output-prerender.test.ts`
ran in the webpack prod job and only differs by prerender error ordering
in the inline snapshot.


<!-- NEXT_JS_LLM_PR -->

---------

Co-authored-by: Benjamin Woodruff <[email protected]>
2026-06-15 23:19:53 +00:00

153 lines
5.1 KiB
TypeScript

import { isNextDeploy, nextTestSetup } from 'e2e-utils'
import { retry } from 'next-test-utils'
// `experimental.turbopackWorkerAssetPrefix` is turbopack-only.
const isTurbopack = !process.env.IS_WEBPACK_TEST && !process.env.NEXT_RSPACK
const describeTurbopack =
isTurbopack && !isNextDeploy ? describe : describe.skip
// CORS so cross-origin script tags from `assetPrefix` can be fetched. Workers
// are NOT covered by CORS — `new Worker(crossOriginUrl)` is rejected
// regardless — so this only unblocks regular script loading.
const corsHeadersConfig = `
async headers() {
return [
{
source: '/:path*',
headers: [{ key: 'Access-Control-Allow-Origin', value: '*' }],
},
]
},`
/**
* Real cross-origin setup: the page is served at `http://localhost:PORT/`,
* `assetPrefix` points to `http://127.0.0.1:PORT` (different origin —
* browsers treat `localhost` and `127.0.0.1` as distinct origins). Both
* resolve to the same Next.js server bound to all interfaces.
*
* The fixture intercepts `new Worker()` to capture the URL the turbopack
* runtime helper resolved from `turbopackWorkerAssetPrefix`, so each test
* can assert on that URL directly.
*/
describeTurbopack('turbopack-worker-asset-prefix', () => {
describe('without turbopackWorkerAssetPrefix (cross-origin assetPrefix)', () => {
const { next } = nextTestSetup({
files: __dirname,
skipStart: true,
forcedPort: 'random',
})
beforeAll(async () => {
const port = next.forcedPort
await next.patchFile(
'next.config.js',
`module.exports = {
assetPrefix: 'http://127.0.0.1:${port}',${corsHeadersConfig}
}`
)
await next.start()
})
it('Worker URL inherits assetPrefix and the browser rejects construction', async () => {
const browser = await next.browser('/')
const forcedPort = next.forcedPort
await retry(async () => {
const url = await browser.elementByCss('#worker-ctor-url').text()
expect(url).toContain('http://127.0.0.1:')
expect(url).toContain(`:${forcedPort}/`)
})
// Cross-origin Worker construction throws SecurityError synchronously.
await retry(async () => {
const error = await browser.elementByCss('#worker-ctor-error').text()
expect(error).toBe('SecurityError')
})
})
})
describe('with turbopackWorkerAssetPrefix overriding assetPrefix', () => {
const { next } = nextTestSetup({
files: __dirname,
skipStart: true,
forcedPort: 'random',
})
beforeAll(async () => {
const port = next.forcedPort
await next.patchFile(
'next.config.js',
`module.exports = {
assetPrefix: 'http://127.0.0.1:${port}',
experimental: {
// Route Worker URLs through the page's own origin
// ('http://localhost:PORT') instead of the cross-origin assetPrefix.
turbopackWorkerAssetPrefix: 'http://localhost:${port}',
},${corsHeadersConfig}
}`
)
await next.start()
})
it('Worker URL uses the override origin and construction succeeds', async () => {
const browser = await next.browser('/')
const forcedPort = next.forcedPort
await retry(async () => {
const pageOrigin = await browser.elementByCss('#page-origin').text()
const url = await browser.elementByCss('#worker-ctor-url').text()
expect(pageOrigin).toBe(`http://localhost:${forcedPort}`)
expect(url.startsWith(pageOrigin)).toBe(true)
expect(url).not.toContain('127.0.0.1')
})
const error = await browser.elementByCss('#worker-ctor-error').text()
expect(error).toBe('(none)')
})
})
describe('with turbopackWorkerAssetPrefix: "" (literal empty prefix)', () => {
const { next } = nextTestSetup({
files: __dirname,
skipStart: true,
forcedPort: 'random',
})
beforeAll(async () => {
const port = next.forcedPort
await next.patchFile(
'next.config.js',
`module.exports = {
assetPrefix: 'http://127.0.0.1:${port}',
experimental: {
// Empty string is a literal empty prefix (only '/_next/' is
// appended). It does NOT fall back to assetPrefix — only
// 'undefined' does.
turbopackWorkerAssetPrefix: '',
},${corsHeadersConfig}
}`
)
await next.start()
})
it('Worker URL is a relative /_next/ URL (resolved same-origin)', async () => {
const browser = await next.browser('/')
const forcedPort = next.forcedPort
await retry(async () => {
const pageOrigin = await browser.elementByCss('#page-origin').text()
const url = await browser.elementByCss('#worker-ctor-url').text()
expect(pageOrigin).toBe(`http://localhost:${forcedPort}`)
// URL passed to `new Worker(...)` lives on the page's origin, not
// assetPrefix. (Internally the runtime resolves the relative
// `/_next/...` against `location.origin`.)
expect(url.startsWith(pageOrigin)).toBe(true)
expect(url).not.toContain('127.0.0.1')
})
const error = await browser.elementByCss('#worker-ctor-error').text()
expect(error).toBe('(none)')
})
})
})