no-restricted-paths: `deep` mode

[benmosher]

In addition to checking resolved imported paths for restrictions, could also deeply traverse the imports of imports and report if there is any deep module dependency on a restricted path.

Would not be necessary if you are linting all the dependencies together, since the root module would report the original import, but could be useful in a context like Sublime where a deep relationship might have snuck in elsewhere (like a git pull).

Would also be useful if all the intermediate dependencies are not being linted. This would be able to traverse imported node_modules if ES6 was available (e.g. via jsnext:main).

@lo1tuma: thoughts?

[lo1tuma]

Personally I don’t have such a use-case.

Is there any specific demand for such a feature?

[benmosher]

Nope, just dawned on me that it would be possible.

I do occasionally have things like jQuery sneak into my Node server processes via deep shared code, and it's often not easy to figure out what intermediate dependency caused it. But I think the rule as you have designed it, if properly configured, could help considerably with that without this "deep" mode.

So probably not necessary.