import-js/eslint-plugin-import

Resolvers naming convention for scoped packages

Open

#1,077 opened on Apr 12, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (1,540 forks)batch import
acceptedenhancementhelp wantedresolver

Repository metrics

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

Description

Hi!, thanks for this library, it's super useful. I just published @5rabbits/eslint-import-resolver-directory-named and It would be great if scoped packages follows the eslint-import-resolver-* convention), so that users can include it like this:

settings:
  import/resolver: @5rabbits/directory-named

Currently I'm using the full package name import/resolver: @5rabbits/eslint-import-resolver-directory-named, but it's kinda verbose 😞.

Contributor guide

Research direction
Investigate how the plugin resolves resolver names from settings.import/resolver and modify to support scoped package naming convention (e.g., @scope/eslint import resolver *).
Tech stack
javascriptnodejs
Domain
developer experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Clear
Prerequisites
ESLint plugin developmentnpm scoped packages
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70