import-js/eslint-plugin-import

Tests: figure out why webpack resolver fails when webpack is present

Open

#1,987 opened on Feb 7, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,540 forks)batch import
help wantedpackage: resolver/webpack

Repository metrics

Stars
 (4,946 stars)
PR merge metrics
 (Avg merge 138d 22h) (3 merged PRs in 30d)

Description

See d108b5d3aafc0e20aa3c08ad85b0ecfe184ad552 and #1986.

Contributor guide

Research direction
Examine the commit d108b5d3aafc0e20aa3c08ad85b0ecfe184ad552 and issue #1986 to understand the webpack resolver test failure.
Tech stack
javascript
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65