
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";
This change accommodates a TypeScript limitation: a default type import cannot be combined with named type imports in a single declaration.
Bug Fixes
Documentation
ab7c625docs: Update README (GitHub Actions Bot)dae1e5bdocs: update jsdoc’s link (#19896) (JamesVanWaza)
Chores
b035f74chore: upgrade to@eslint/[email protected](#19906) (Francesco Trotta)b3dbc16chore: package.json update for @eslint/js release (Jenkins)

