We investigated the failing tanstack-vue-start-e2e-basic:test:e2e--vite-ssr--shard-1-of-4 task and found it is unrelated to our PR changes. The error is a missing getDummyServerPort export in the compiled e2e/e2e-utils/dist/esm artifact — a stale build from a prior, unrelated change. Our PR does not touch any e2e-utils files, so a rebuild of that package in the CI environment should resolve this.
Self-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 errors with:
SyntaxError: The requested module './derivePort.js' does not provide an export named 'getDummyServerPort'
This error originates in a compiled build artifact located at e2e/e2e-utils/dist/esm/e2eSetupTeardown.js, not in source code.
The PR diff was inspected for any changes to e2e-utils, derivePort, or getDummyServerPort — none were found. The PR is scoped entirely to fixing lazy route component reuse across React, Solid, and Vue routers.
The flakiness rate for this task is 0%, ruling out a flaky classification.
No similar failures were detected in branch 8055, ruling out a known recurring infrastructure issue.
The root cause is a stale dist artifact: the e2e-utils package was not rebuilt after a source-level change (adding the getDummyServerPort export to derivePort.ts) was made in a prior, unrelated change. Since this is a pre-existing build environment inconsistency not introduced by the PR, it is classified as environment_state.