react-doctor/tanstack-start-missing-scripts
Root route missing Scripts
- Category: Bugs
- Severity: warn
- Source:
oxlint-plugin-react-doctor - Framework: tanstack-start
- Enabled when: tanstack-start
- Tags: test-noise
- Default: Enabled
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Confirm the reported code matches react-doctor/tanstack-start-missing-scripts. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.
Compare the code
The corrected pattern shows a focused way to address the diagnostic.
Reported pattern
import {
createRootRoute,
Outlet,
} from "@tanstack/react-router";
export const Route = createRootRoute({
component: () => (
<html lang="en">
<body>
<Outlet />
</body>
</html>
),
});Corrected pattern
import {
createRootRoute,
Outlet,
Scripts,
} from "@tanstack/react-router";
export const Route = createRootRoute({
component: () => (
<html lang="en">
<body>
<Outlet />
<Scripts />
</body>
</html>
),
});How to fix
Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.
Copyable fix prompt
Copy this self-contained prompt into your coding agent after you confirm the diagnostic.
Fix every confirmed
Reference transformation:Before:react-doctor/tanstack-start-missing-scripts diagnostic in the current repository.
Required change:
- Render <Scripts /> near the end of <body> in your __root route so TanStack Start can load client-side JavaScript.import {
createRootRoute,
Outlet,
} from "@tanstack/react-router";
export const Route = createRootRoute({
component: () => (
<html lang="en">
<body>
<Outlet />
</body>
</html>
),
});import {
createRootRoute,
Outlet,
Scripts,
} from "@tanstack/react-router";
export const Route = createRootRoute({
component: () => (
<html lang="en">
<body>
<Outlet />
<Scripts />
</body>
</html>
),
});Constraints:
- Confirm the reported code matches the Before pattern.
- Make the smallest change that fixes the root cause.
- Preserve behavior and interfaces unrelated to this diagnostic.
- Reuse existing project components, utilities, and conventions.
- Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
- Adapt identifiers and framework details instead of copying blindly.
- Do not disable the rule or suppress matching code.
- Confirm this rule is enabled for the project:
tanstack-start.
Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears.
- Report the files changed and any checks you could not run.Related rules
More Bugs rules from the rules reference:
react-doctor/tanstack-start-no-anchor-element: `import { Link } from '@tanstack/react-router'` — enables type-safe routes, preloading via `preload="intent"`, and client-side navigationreact-doctor/tanstack-start-no-direct-fetch-in-loader: Use `createServerFn()` from @tanstack/react-start — provides type-safe RPC, input validation, and proper server/client code splittingreact-doctor/tanstack-start-no-dynamic-server-fn-import: Use `import { myFn } from '~/utils/my.functions'` — the bundler replaces server code with RPC stubs only for static importsreact-doctor/tanstack-start-no-navigate-in-render: Use `throw redirect({ to: '/path' })` in `beforeLoad` or `loader` instead — navigate() during render causes hydration issuesreact-doctor/tanstack-start-no-use-server-in-handler: TanStack Start handles server boundaries automatically via the Vite plugin — "use server" inside createServerFn causes compilation errors