import-js/eslint-plugin-import

expose semi-core modules via resolvers

Open

#479 opened on Aug 8, 2016

View on GitHub
 (6 comments) (7 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
enhancementhelp wantedresolversemver-major

Description

https://github.com/clayne11/eslint-import-resolver-meteor/issues/11

TL;DR: semi-magic modules (in this case, meteor/*) that exist on disk (and thus can be linted) but are baked into the environment (and thus, are not explicitly dependencies) ideally should not blow up no-extraneous-dependencies.

Hand-wavy possible solution: allow resolvers to define import types somehow. (maybe move the importType functionality down into the resolver spec?)

Or could keep the existing behavior when/if chosen resolver does not explicitly provide the designation.

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.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 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.
needs investigation
Prerequisites
ESLint plugin architectureimport resolutionNode.js module system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the current resolver implementation in eslint plugin import (likely in src/resolvers/). Review the linked issue for context on how meteor/* modules cause false positives for no extraneous dependencies. Propose a design for allowing resolvers to specify import types, possibly by adding a method or metadata to the resolver spec. Consider backwards compatibility and ensure existing resolvers continue to work. Document the approach and get feedback from maintainers.