We identified that all three e2e failures are caused by a pre-existing Babel/TypeScript transpilation error in packages/router-core/src/router.ts (the declare field at line 1104), which also appears in the base branch (#8165) this PR is stacked on. Our PR only adds regression tests and does not touch router-core or any of the affected projects, so these failures are unrelated to the changes introduced here.
Failed after
SSheraffView latestperf(router-core): omit unused initial lifecycle boundary
8243a543994Open 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.
All three failing tasks — tanstack-react-start-e2e-dev-ssr-styles:test:e2e, tanstack-router-e2e-react-scroll-restoration-sandbox-vite:test:e2e, and tanstack-react-start-e2e-basic-scroll-restoration:test:e2e — fail with an identical SyntaxError:
SyntaxError: /home/workflows/workspace/packages/router-core/src/router.ts:
TypeScript 'declare' fields must first be transformed by @babel/plugin-transform-typescript.
The error points to line 1104 of packages/router-core/src/router.ts, where a declare _lifecycleEnd?: number field triggers a Babel plugin ordering conflict unrelated to the PR's changes.
This PR only adds regression tests for react-router context behavior during pending navigation and not-found handling. The touched_projects list is empty ([]), confirming no project files were modified by this PR that could affect the failing tasks.
The same error was confirmed to exist in branch 8165 — the base branch this PR is explicitly stacked on — meaning the failure pre-dates and is independent of this PR's changes.
With a flakiness rate of 0% for all three tasks, the failures are deterministic and not timing-related. They stem from a pre-existing Babel/TypeScript transpilation misconfiguration in router-core introduced upstream, not by anything in this PR.