ESLint v9.30.1 released

Highlights

Separate default and named type import declarations in no-duplicate-imports

The no-duplicate-imports rule now allows both a default type import and named type imports from the same module in separate declarations.

import type A from "some-module";
import type { B, C } from "some-module";
1
2

This change accommodates a TypeScript limitation: a default type import cannot be combined with named type imports in a single declaration.

Bug Fixes

• e91bb87 fix: allow separate default and named type imports (#19899) (xbinaryx)

Documentation

• ab7c625 docs: Update README (GitHub Actions Bot)
• dae1e5b docs: update jsdoc’s link (#19896) (JamesVanWaza)

Chores

• b035f74 chore: upgrade to @eslint/js@9.30.1 (#19906) (Francesco Trotta)
• b3dbc16 chore: package.json update for @eslint/js release (Jenkins)