import-js / import-js/eslint-plugin-import
Tests: figure out why webpack resolver fails when webpack is present
Open
Nobody has claimed this yet.
help wanted
package: resolver/webpack
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
See d108b5d3aafc0e20aa3c08ad85b0ecfe184ad552 and #1986.
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 reviewing commit d108b5d3aafc0e20aa3c08ad85b0ecfe184ad552 and issue #1986, then trace the webpack resolver test path they reference. Done means identifying why resolution fails when webpack is present and documenting or addressing that failure with a reproducible test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- testing-qa, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100