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 (4,946 stars) (1,540 forks)batch import
acceptedenhancementhelp wantedresolver

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

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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
clear
Prerequisites
familiarity with eslint plugin architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue requests supporting a shorthand resolver name for scoped packages (e.g., @scope/resolver instead of @scope/eslint import resolver resolver). Investigate the resolver loading logic in eslint plugin import, likely in the `resolve` or `resolvers` module. Check if there's a pattern for stripping the `eslint import resolver ` prefix. The existing resolvers are loaded by looking for a package named `eslint import resolver <name>`. For scoped packages, the convention should map `@scope/name` to `@scope/eslint import resolver name`. Review the codebase for how resolvers are resolved and consider adding support for scoped packages.