import-js/eslint-plugin-import

expose semi-core modules via resolvers

Open

#479 创建于 2016年8月8日

在 GitHub 查看
 (6 评论) (7 反应) (0 负责人)JavaScript (1,540 fork)batch import
enhancementhelp wantedresolversemver-major

仓库指标

Star
 (4,946 star)
PR 合并指标
 (平均合并 138天 22小时) (30 天内合并 3 个 PR)

描述

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.

贡献者指南