Ben Mosher

haven't looked closely at code but I like the idea 👍

ideally everything that is acting on arbitrary imports/requires should go through moduleVisitor so we can centralize the detection. I'd also like to (if it doesn't already) allow setting es/common/amd settings...

@ljharb @hulkish I am not a user of this rule. it's not clear to me based on discussion if this PR is in a useful releasable state. if it is...

I would merge but it's not clear to me why there are conflicts nor how to resolve them for the issues you are all facing. @hulkish are you able to...

my normal tack in a loop (when there is no `.join(" ")` in the platform): ```rust if !sentence.is_empty() { sentence += " " } sentence += *word; ``` (no idea...

Should be, could hardcode `meteor` as an un-pathed dependency (would need to return `{ found: true, path: null }` from the resolver).

or maybe at this line, replace `meteor/` with `meteor`? https://github.com/clayne11/eslint-import-resolver-meteor/blob/master/index.js#L15

Ah, yeah, actually, I misunderstood the issue at first. I think you could use the [`import/core-modules` setting](https://github.com/benmosher/eslint-plugin-import#importcore-modules) to ignore it. Will treat it as a built-in. ``` yaml # .eslintrc.yml...

interesting, I think maybe the issue is that "core" modules are not properly ignored by `import/extensions` when they are core relative to a specific module.