Remove use of webpack alias

[Pezmc]

Description

Using webpacks non ES standard aliases looks slightly nicer but breaks one of the key advantages of ES modules, static analysis.

Our aliases e.g. @:

• Lock us to webpack making it harder to swap to another tool
• Prevent lots of tooling from working correctly, including VSCodes "open file" shortcuts.
• Prevent static analysis, e.g. eslint checking all files exist
• Doesn't autocomplete
• Make it harder to differentiate the scope of the component
• Encourage shared components not being placed in a shared components folder

Example: elastic/kibana#6430

Epic/Story

No response

[Steve-Mcl]

Fab - cannot wait for this to be merged.

One question @Pezmc can we (should we) also add the file extension to the imports? i.e. be more explicit.

It may not be an issue now you are moving away from aliases but for my own dev env, I had a temporary jsconfig,json file to help VSCode resolve the aliases (for intellisense, navigation, type hints etc) but the vue files still needed the .vue extension for navigation to work. Basically, around half of our page imports have them and half do not.

Thoughts please?

[Pezmc]

Yes, I'd lean towards explicitly adding .vue, the handling of .vue is also a custom webpack handling so am 👍 to adding it to decouple us from webpack and improve static code analysis.

Can I handle that as a follow up?

[Steve-Mcl]

Can I handle that as a follow up?

Sure thing.

[Pezmc]

Done in #1910 @Steve-Mcl