import-js / import-js/eslint-plugin-import
eslint-plugin-import upgrade issues on no-cycle
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
The upgrade of `eslint-plugin-import` from version` 2.26.0 to 2.31.0`(to support **_flat config_**) has resulted in **increased processing time for ESLint**, primarily due to the **import/no-cycle** rule. Included screenshot as well
```
"import/no-cycle": [
2,
{
"maxDepth": null,
"ignoreExternal": false
}
],
```
I followed this **github thread** and played with those configs(like toggling `disableScc`), but no luck. Can someone assit on this ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the ESLint processing-time increase when upgrading eslint-plugin-import from 2.26.0 to 2.31.0 with the shown import/no-cycle configuration. Compare the behavior while testing the mentioned disableScc setting and consult the linked GitHub thread; done means identifying the cause and a confirmed resolution for the regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100