Eslint rule: enforce no import extensions

[samturrell]

Hi all,

This has come up on another project, where there was an inconsistency on imports, and whether or not they should have a file extensions. E.g.:

import '.../../MyComponent/MyComponent.vue';
import '.../../lib/something.js';

vs

import '.../../MyComponent/MyComponent';
import '.../../lib/something';

The extension is only ever required if a loader is not set up for a specific file type, it cannot be resolved, or if there's ambiguity around (e.g. a directory with both MyComponent.vue and MyComponent.js or a file that also resolves a folder such as import 'store'; might be ambiguous with ./store.js and ./store/index.js.

What are your thoughts here? There's a linter rule we can use to automate this and remove it from any future discussions on a PR level

[cannibble]

I'm inclined to want the extension visible, just makes it easier to decipher what is being imported without knowing about loaders.

[cj11489]

Agreed. I like everything to be explicit, plus avoids the potential ambiguity you mentioned @samturrell

[samturrell]

Agreed. I like everything to be explicit, plus avoids the potential ambiguity you mentioned @samturrell

Worth mentioning though that the odds of that ambiguity happening is very rare

[cj11489]

Yeah true. Its mainly personal preference

[BeccaAnderton]

I agree with @samturrell - I don't see a need to have the extension visible for imports