Allow `import-x` plugin, not only `import`
envgap__import-js__eslint-import-resolver-typescript-293
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
b777b44dcd0e967807f34b45e808c61ca751aa62- Manifest
package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
import-js/eslint-import-resolver-typescript #293 · read the original issue
There is a line in `package.json`: https://github.com/import-js/eslint-import-resolver-typescript/blob/ca11f1c538714252ff058a8e1c680796ee5775d0/package.json#L66 That causes warning during the installation of this package when using `eslint-plugin-import-x`: ``` warning " > eslint-import-resolver-typescript@3.6.1" has unmet peer dependency "eslint-plugin-import@*". ``` Though, even the Readme file suggest to try it (under its former name): > This plugin adds [TypeScript](https://www.typescriptlang.org/) support to [eslint-plugin-import](https://github.com/import-js/eslint-plugin-import) (Or maybe you want to try [eslint-plugin-i](https://github.com/un-es/eslint-plugin-i) for faster speed) I'd like to request either marking that dependency as optional peer (using `peerDepedenciesMeta` entry) or ask for another solution on how these two packages can be installed together without warning.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]