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 (1,540 forks)batch import
enhancementhelp wantedresolversemver-major

Repository metrics

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

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

Research direction
Examine how resolvers currently handle import types and consider extending the resolver spec to allow defining import types for semi core modules. Look at the `no extraneous dependencies` rule to understand how it determines extraneous dependencies.
Tech stack
javascript
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.
1-2 days
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
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65