Multiple slashes in path doesn't throw error on windows.

[bsouthga]

A "nice" difference between *nix and windows systems is that unix treats duplicate slashes in paths /User/ben////my////path/// As one slash /User/ben/my/path/.

Windows however does not. This means that on windows, the module loader will be unable to find paths that are okeyed by the linter, for example:

// fine on unix, bad on windows...
import workflow from './/workflow';

Is there a way we could add a platform specific check? or maybe just disallow duplicate slashes, as they will be removed automatically on unix?

[benmosher]

Yeah, sounds like a good thing to do, in addition to checking that the actual filesystem case matches.

[danny-andrews]

Ran into this issue today. Maybe we could name the rule no-multiple-slashes. Either that or make a general rule called no-extraneous-slashes which could optionally check for trailing slashes, e.g. import workflow from './workflow/';.

[danny-andrews]

@bsouthga As a workaround, you can use the no-restricted-imports rule with a **// pattern. Example config:

rules:
  no-restricted-imports:
    - error
    - patterns: ['**//']

[ljharb]

I'm going to close this as a duplicate of #471, since #912's no-useless-path-segments rule should presumably cover it.