add universal path alias in webpack.partial.conf.resolve

[anicarrr]

Always wanted to add this to the skeleton. It is useful when you are deep in the folder structure. It's more powerful with typescript.

[ThaNarie]

Personally I'm not a big fan of this:

• it's not needed if you have auto-import
• every tool that "analyses" your code needs to configure those aliases as well (typescript, eslint, etc)

[ReneDrie]

We had something similar like this before right (~)? But this was removed because of reasons I don't know

[ThaNarie]

@ReneDrie Are you not confused with the css-loader?

To import assets from a node_modules path (include resolve.modules) and for alias, prefix it with a ~:

url(~module/image.png) => require('module/image.png')
url('~module/image.png') => require('module/image.png')
url(~aliasDirectory/image.png) => require('otherDirectory/image.png')

Or did we have something similar for JS as well?

[anicarrr]

assets don't have auto-import

[ThaNarie]

In my opinion, if possible, assets should live in the same "folder" as the code that uses it.
So we would only have this for more global assets that are used in multiple components?

We already have asset: path.resolve(config.projectRoot, 'src/asset'), for specifically that purpose, so with that I don't see the added benefit of an alias to the src folder itself.

Could you convince me otherwise? :)