FRONT013warningPro

step-state-no-history

Multi-step flow uses useState without browser history — back button exits the app

Applies to: JavaScript, TypeScript

Why this matters

When a multi-step flow (booking wizard, onboarding, form wizard) tracks its current step in a plain useState, the browser has no idea the user navigated between steps. Clicking the back button doesn't go to the previous step — it leaves the app entirely. Sync step state with the URL via useSearchParams, router.push, or window.history.pushState so back/forward navigation works.

Catch it before it ships

pip install stablestack # or: npx stablestackstablestack # scans your project, FRONT013 includedstablestack explain FRONT013

FRONT013 is part of the Pro rule set. See pricing — the free tier ships 24 checks with no signup.

False positive in your codebase? Suppress a single line with # noqa: FRONT013

More Frontend checks

tabs-url-routing

MUI Tabs should use URL routing via useSearchParams for bookmarkable/shareable tabs.

window-ssr-unsafe

Accessing window/document without SSR check causes server-side errors

inline-jsx-handler

Inline arrow functions in JSX cause unnecessary re-renders

nextjs-redirect-request-url

Redirect uses request.url as URL base, which is wrong behind a reverse proxy.

useeffect-side-effect-unguarded

useEffect contains a mutating HTTP call without a guard against double-firing.

stale-time-dependent-ui

Time-dependent filtering without a re-render timer will show stale data.

unbounded-ai-output

AI/LLM output rendered in JSX without truncation or overflow handling.

loading-returns-null

Returning null during loading causes layout shift and flash of empty content.