v27.0.0

27.0.0 (2026-10-19)

• feat(eslint,oxlint)!: enforce type imports with inline specifiers (#251) (285a98a)

BREAKING CHANGES

• The TypeScript presets of @peerigon/configs/eslint
  and @peerigon/configs/oxlint now warn when a regular import is only
  used as a type (import { A } from "a" → import type { A } from "a")
  and when an import only contains inline type specifiers (import { type A } from "a" → import type { A } from "a"). Projects that lint with
  --max-warnings 0 or --deny-warnings will fail until these imports
  are fixed. Both rules are autofixable: eslint --fix fixes everything
  in one run, oxlint --fix needs a second run because it first rewrites
  import { A } to import { type A }. Under verbatimModuleSyntax the
  fixed imports are removed from the emitted JavaScript entirely, so code
  that relied on the side effects of a module that was only imported for
  its types must add an explicit import "a".

🤖 Generated with Claude Code

Co-authored-by: Claude Opus 5.5 (1M context) noreply@anthropic.com