We identified that this failure is unrelated to the PR's changes. The test crashes before execution due to a stale build artifact in e2e/e2e-utils/dist/esm/index.js, where a named export toRuntimePath no longer exists in the compiled output. Rebuilding the e2e-utils package should resolve this environment state issue.
Failed after CPCong-Cong Pan
Merge remote-tracking branch 'upstream/main' into fix-tanstack-router-dev
7685bf247d6Open on GitHubSelf-Healing CI
Classification: Environment state
No code changes are applicable.
The failing task tanstack-react-start-e2e-basic:test:e2e--rsbuild-ssr--iife crashes before any test runs with:
SyntaxError: The requested module './to-runtime-path.js' does not provide an export named 'toRuntimePath'
at file:///home/workflows/workspace/e2e/e2e-utils/dist/esm/index.js:3
The error originates in e2e/e2e-utils/dist/esm/index.js — a pre-built dist artifact.
The PR does not touch any file under e2e/e2e-utils/. The dist file references a named export (toRuntimePath) that no longer exists in the compiled module, which is a classic stale-build mismatch: the source of e2e-utils was updated at some point but the dist was not rebuilt before the tests ran.
The PR's changes are limited to:
- Fixing rsbuild import-protection logic in
packages/start-plugin-core/src/rsbuild/import-protection.ts - Adding a new e2e fixture under
e2e/react-start/rsbuild/ - Bumping
@rsbuild/coreversions across severalpackage.jsonfiles
None of these changes involve e2e-utils or could cause the named-export mismatch seen in the error.
The flakiness rate for this task is 0%, ruling out a flaky classification. No similar errors were found in other branches, confirming this is not a widespread regression.
The fix requires rebuilding the e2e-utils package so its dist output matches the current source — an environment/infrastructure action, not a code change in this PR.