import-js / import-js/eslint-plugin-import
eslint-import-resolver-webpack and import-first
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
`eslint-import-resolver-webpack` is integrated into [`react-boilerplate`](https://github.com/mxstbr/react-boilerplate), nonetheless, we got a bunch of `Absolute imports should come before relative imports` errors for imports like `'containers/LanguageProvider'` that are actually local, as they're resolved with `webpack`.
Is this an expected behavior or a bug?
Contributor guide
Research direction
Reproduce the reported errors in react-boilerplate with eslint-import-resolver-webpack and the import-first rule, focusing on imports such as containers/LanguageProvider. Determine whether the resolver or rule is misclassifying these local webpack-resolved imports, and document the expected behavior and required change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100