We investigated this E2E failure and determined it is unrelated to the PR's changes. The error originates in a pre-built e2e/e2e-utils dist artifact that is missing the resolveRuntimeSuffix export, indicating the package was not rebuilt before the test suite ran in CI. Our changes are scoped entirely to @tanstack/router-plugin and have no effect on this artifact.
Failed after
LladybluenotesView latestperf(router-plugin): avoid redundant compiler work
82762311940Open on GitHubSelf-Healing CI
Classification: Environment state
An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.
The failing task is tanstack-solid-start-e2e-basic:test:e2e--vite-ssr--shard-1-of-4, which belongs to a project not touched by this PR.
The PR exclusively modifies files within @tanstack/router-plugin (compiler logic, the code-splitter plugin, and related tests) plus a changeset entry. It makes no changes to e2e/e2e-utils or any solid-start E2E infrastructure.
The error itself — SyntaxError: The requested module './resolve-runtime-suffix.js' does not provide an export named 'resolveRuntimeSuffix' — originates in e2e/e2e-utils/dist/esm/index.js, a pre-built dist artifact. This means the compiled output in the dist/esm directory is out of sync with its source; specifically, resolve-runtime-suffix.js is missing the resolveRuntimeSuffix export that index.js expects.
There is no code path from the PR's changes to this artifact mismatch.
Additionally, the task's flakiness rate is 0%, ruling out a non-deterministic test issue, and no similar failure was found in other branches, confirming this is not a pre-existing upstream regression.
The root cause is a stale or incorrectly built e2e/e2e-utils dist in the CI environment, which must be resolved at the environment level (e.g., by ensuring the package is rebuilt before the E2E suite runs).