Prevent relative client-side redirects in Next.js with an ESLint rule

Prevent relative client-side redirects in Next.js with an ESLint rule targets a $12.0B = 24M active software developers x $500 avg. annual spend on dev tooling, static analysis, and CI integrations total addressable market with medium saturation and a year-over-year growth rate of 8-12% — developer tools and static analysis markets growing with cloud-native adoption and increasing CI/quality budgets.

Key trends driving demand: AI-generated code -- LLMs often output quick client-side hacks (like direct location assignments) that bypass framework routing conventions, increasing demand for automated linting.; Framework-specific tooling -- Teams prefer framework-aware linters and rules (React/Next.js) over generic static analysis because they capture runtime conventions.; Shift-left security/quality -- Organizations push checks into developer workflows and CI, raising the value of small, fast rules that block common bugs.; IDE/CI integration standardization -- ESLint rules propagate quickly via editor plugins and CI pipelines, enabling rapid enterprise adoption of new rules..