import-js/eslint-plugin-import

Respect ResolverPlugins

Open

#165 opened on Feb 3, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
enhancementhelp wanted

Description

I use webpack-directory-name-as-main, but in general the resolver should apply the plugins to its own work.

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingdeveloper experience
Issue type
feature
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
eslint plugin import resolver architecturewebpack resolver pluginsJavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the current resolver implementation in the eslint plugin import codebase, particularly how plugins are handled. Identify where resolver plugins are ignored and where they should be applied. Review the behavior of webpack directory name as main as an example and design a solution to ensure resolver plugins are respected during module resolution.