Speed up webpack build

[bru02]

Implement #44

[KaelWD]

We had a lower-maintenance version of this previously: 3fea882

It may cause css problems as there is no longer a defined import order.

[kevinmarrec]

@KaelWD It looks like that since your previous lower-maintenance version, you made imports sorted (https://github.com/vuetifyjs/vuetify-loader/blob/master/lib/loader.js#L31) could it prevent any css issue ?

I don't know much about the importance of css import orders but webpack build definitely need speed up, as for now a single import { VBtn } from 'vuetify/lib' webpack will still look for all components within vuetify/lib which means also all of their SASS files and that's too heavy extra processing.

Maybe it's an issue regarding how are exported components in vuetify/lib ? I know that some ways of using import/export (maybe export * from) are not treeshakable.
EDIT : It's anyway treeshaked but it still make Webpack compile/build all exports, so I think best solution is still this PR making vuetify-loader import components from their direct folders vuetify/lib/components/X.

[KaelWD]

made imports sorted

That was to fix vuetifyjs/vuetify#5271, didn't work

We do still have ordering problems (vuetifyjs/vuetify#3583) so maybe it won't be a problem. Either way I'd prefer to use my original code without hard-coded workarounds, we added structures to the vuetify repo specifically for this reason.

[kevinmarrec]

@KaelWD I totally agree around the added structures, but something that is annoying is that Webpack seems to just go crazy and load/process everything when you simply do impport { VBtn } from 'vuetify/lib'.

For a little project which use only few components, ther's probably 80% unwanted webpack processing (lot of reached files which will be never used, it includes the loading and processing of unwanted SASS files of all components).

I think the issue has something to do with exports somewhere.

[KaelWD]

I'm referring to 3fea882 of course

Webpack processes everything and marks what's actually unused, then the minifier actually removes unused code.

[kevinmarrec]

Oh alright, I thought it was a performance issue (seeing all the Vuetify file names processed in Webpack bar progress)

[KaelWD]

Thanks for taking the time to do this @bru02. I've merged it into a feature branch for now because there's some changes I want to make before release.

[johnleider]

Is this still something you are pursuing @KaelWD ?

[KaelWD]

No, it was released in 1.3