npm / @metamask/eslint-config
@metamask/eslint-config
What changed in @metamask/eslint-config 14 to 15, from its official release notes, upgrade guides and advisories. Also covers @metamask/eslint-config-jest, @metamask/eslint-config-mocha, @metamask/eslint-config-nodejs, @metamask/eslint-config-typescript. Sources checked 2026-10-19.
3 breaking5 behavior and defaults5 tooling2 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@metamask/eslint-config 1510 changes
Breaking changes 3
This replaces
@typescript-eslint/consistent-type-importsand prefers top-level type imports over inline type imports.The peer dependency requirement is bumped from ^14.0.0 to ^15.0.0.
The peer dependency minimum version is raised to v8.39.0.
Behavior and default changes 2
Naming conventions are no longer enforced for object literal properties.
The rule is disabled, allowing type arguments considered unnecessary by the rule.
Tooling 3
The rule is disabled due to problems with indented sections in TSDoc blocks.
The rule is disabled because it is redundant in type-checked projects.
The peer dependency is widened to allow all 5.x versions.
Fixes and other changes 2
The TypeScript ESLint config can now be imported from CommonJS.
The rule is disabled; its auto-fix was broken and could group non-type imports under a type import.
@metamask/eslint-config 145 changes
Behavior and default changes 3
Allows more formats for import names.
Loosens the rule to allow rejecting with
unknown.Loosens the rule to allow a
defaultcase.
Tooling 2
Disables this ESLint rule.
Adds support for TypeScript 5.6.x–5.8.x.