# What changed in @next/eslint-plugin-next

> 5 changes in @next/eslint-plugin-next 16 from its official release notes, upgrade guides and advisories: 3 breaking. Each one cited. Sources checked 2026-10-27. HTML: https://unstale.sh/npm/@next/eslint-plugin-next/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## @next/eslint-plugin-next 16

### Breaking changes

- The command no longer runs linting, so run linting separately. (16.0.0) — [upgrade guide](https://nextjs.org/docs/pages/guides/upgrading/version-16)
- The plugin now defaults to ESLint Flat Config format, aligning with ESLint v10, which will drop legacy config support. (16.0.0) — [upgrade guide](https://nextjs.org/docs/pages/guides/upgrading/version-16)
- The command has been removed; use Biome or ESLint directly. (16.0.0) — [upgrade guide](https://nextjs.org/docs/pages/guides/upgrading/version-16)

### Behavior and default changes

- The plugin now defaults to ESLint Flat Config format; users of legacy .eslintrc should consider migrating. (16.0.0) — [upgrade guide](https://nextjs.org/docs/app/guides/upgrading/version-16)

### Tooling

- The upgrade codemod migrates projects from next lint to the ESLint CLI. (16.0.0) — [upgrade guide](https://nextjs.org/docs/app/guides/upgrading/version-16)