Rule proposal: warn when import uses ../ too many times

[lencioni]

I'm not sure if there is a term for this, and describing it is a bit awkward, but I'll give it a shot.

Let's say you have a directory structure like:

/foo/bar/baz.js
/foo/bar/boop.js

In baz.js you want to import boop.js. Normally you would write it like this:

import boop from './boop';

However, if you aren't paying attention, especially when moving code around, you might end up doing something like this instead:

import boop from '../bar/boop';

Or in a more deeply nested structure, you might end up with something like this that overshoots its target:

import boop from '../../../bar/boop';

It would be really great to have a rule that warns against these.

[ljharb]

Perhaps if a relative import path does not match path.normalize() of that path, it warns?

[danny-andrews]

@ljharb Dupe of #471?

[ljharb]

Indeed, this is a duplicate of #471.