import-js / import-js/eslint-plugin-import
expose semi-core modules via resolvers
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No 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
Start with the linked resolver issue and trace the existing importType functionality and resolver specification. Decide how a resolver can designate semi-core modules such as meteor/* while preserving current behavior when no designation is supplied; done means those imports no longer incorrectly trigger no-extraneous-dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100