Upgrading @eslint/eslintrc from 2.x to 3.x
Comparison of the public API of @eslint/eslintrc 2.1.4 and 3.3.7, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 0 |
| Changed class or interface members | 4 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
| member | Before | After |
|---|---|---|
FlatCompat.env | (envConfig: { [name: string]: boolean; }): Linter.FlatConfig[] | (envConfig: { [name: string]: boolean; }): Linter.Config[] |
FlatCompat.config | (eslintrcConfig: Linter.LegacyConfig): Linter.FlatConfig[] | (eslintrcConfig: Linter.LegacyConfig): Linter.Config[] |
FlatCompat.extends | (...configsToExtend: string[]): Linter.FlatConfig[] | (...configsToExtend: string[]): Linter.Config[] |
FlatCompat.plugins | (...plugins: string[]): Linter.FlatConfig[] | (...plugins: string[]): Linter.Config[] |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | ^12.22.0 || ^14.17.0 || >=16.0.0 | ^18.18.0 || ^20.9.0 || >=21.1.0 |
Frequently asked questions
What are the breaking changes when upgrading @eslint/eslintrc from 2 to 3?
Between @eslint/eslintrc 2.1.4 and 3.3.7, Vigia found 0 removed exports, 0 changed signatures and 4 removed or changed class or interface members.
What became deprecated in @eslint/eslintrc 3?
0 exports or members are newly marked as deprecated in @eslint/eslintrc 3.3.7.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/@eslint/eslintrc/upgrade?from=2.1.4&to=3.3.7