import-js/eslint-plugin-import
Ver no GitHubexpose semi-core modules via resolvers
Open
#479 aberto em 8 de ago. de 2016
enhancementhelp wantedresolversemver-major
Métricas do repositório
- Stars
- (4.946 stars)
- Métricas de merge de PR
- (Mesclagem média 138d 22h) (3 fundiu PRs em 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.