eslint-plugin-import@"2.14.0" causes peer-dep inconsistency

Description

npm WARN ERESOLVE overriding peer dependency npm WARN Found: eslint-plugin-import@2.14.0 npm WARN ui-calendar/node_modules/eslint-plugin-import npm WARN eslint-plugin-import@"2.14.0" from @folio/eslint-config-stripes@3.2.100038 npm WARN ui-calendar/node_modules/@folio/eslint-config-stripes npm WARN dev @folio/eslint-config-stripes@"^3.2.1" from ui-calendar@6.0.0 npm WARN ui-calendar npm WARN 2 more (eslint-config-airbnb, eslint-import-resolver-webpack) npm WARN npm WARN Could not resolve dependency: npm WARN peer eslint-plugin-import@"^2.17.2" from eslint-config-airbnb-base@13.2.0 npm WARN ui-calendar/node_modules/eslint-config-airbnb/node_modules/eslint-config-airbnb-base npm WARN eslint-config-airbnb-base@"^13.1.0" from eslint-config-airbnb@17.1.0 npm WARN ui-calendar/node_modules/eslint-config-airbnb

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Zak Burke September 22, 2022 at 4:34 PM

This is a little wacky: in fact, we migrated off v2.14.0 back in 2019 (see PR #52) but it continues to creep into builds via UI apps that haven't updated their eslint-config-stripes deps, as seen in ui-calendar in the description here. IOW, the problem is really "UI apps depending on outdated versions of our eslint-conf package" rather than "our eslint-conf package continues to be out of date".

Done

Details

Assignee

Reporter

Priority

Development Team

None

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created May 13, 2021 at 4:07 PM
Updated September 22, 2022 at 4:34 PM
Resolved September 22, 2022 at 4:34 PM
TestRail: Cases
TestRail: Runs