Next.js: New ESLint Rule and Test Improvements

Next.js added a new ESLint rule to prevent incorrect relative URL navigation patterns often generated by LLM models, and fixed flaky shallow routing tests.

Duration: PT1M23S

Episode overview

This episode is a short developer briefing from Next.js.

It explains recent repository work in plain language.

  • Show: Next.js
  • Published: 2026-04-19T00:00:00Z
  • Audio duration: PT1M23S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good evening, this is your Next.js development briefing for April 19th, 2026.

SukkaW merged a new ESLint rule called "no-location-assign-relative-destination" that addresses a specific problem with AI-generated code. The rule detects when developers use location.href or location.assign with relative URLs instead of Next.js's proper navigation methods like redirect() or useRouter().push().…

eps1lon merged a test stability fix for the shallow-routing test suite. The test was occasionally failing due to timing issues where the Router hadn't updated yet, causing intermittent failures in the CI pipeline.

Benjamin Woodruff also committed a maintenance update, pruning the labeler configuration to remove seven unused user entries from the GitHub automation setup.

What's next for the project: The ESLint rule will help developers using AI coding assistants maintain proper Next.js navigation patterns, while the test improvements should reduce CI flakiness. This continues Next.js's focus on developer experience and code quality tooling.

That's your Next.js briefing for today.

Nearby episodes from Next.js

  1. Cache Performance Improvements and Bug Fixes
  2. Turbopack Performance and Cache Improvements
  3. React Upgrade and Documentation Improvements
  4. Weekly Recap - ESLint Improvements and Developer Experience
  5. Logging Refactor and Development Tools Update
  6. Weekly Recap - Turbopack Performance & Developer Experience
  7. Turbo Engine Cleanup and Stream Recovery
  8. Weekly Recap - Infrastructure Overhauls and Developer Experience