-
-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict in order with mini-css-extract-plugin (i know,the question have already been asked several time :-/) #657
Comments
After many hour of investigation, it seems that vue-router, when we load components at the fly with "component: () => import('../main.vue')" break mini-css order. If i load main.vue at the top of the script, with an import no problem ! But it's to me a real problem to load all .vue at the top of the script : loading of the app take several second longer. |
Sorry I can't help, you don't fill out the issue template, so I don't know your version, your configuration, how I can reproduce it or other information, if you need help please fill out all fields in the issue template and I will help, yes order can be changed in some rare cases, but I can't say you why, because I don't see your code |
Thanks for anwser. The problem was between chair and keyboard, like always. If anyone who use electron-webpack / vue-loader / vue-router face this problem : you need to grab all css chunk into one, otherwise webpack do a chunck per route and you can get the "conflict warning order". You can configure webpack in this way :
You can also modify your router in this way (/* webpackChunkName: "app" */)
But this way you grab js and css into a single file, loosing advantages of dynamic load and performance are downgrade @evilebottnawi : can you let me know if i'm right ? this solution seems to walk like a charm but it's the right way ? thanks again for your previously answer ! |
I think yes, it doesn't look bad |
Thanks master ;) |
Hi community, i need your help !
Stack
Electron, electron-webpack, vuejs (vue-loader / vue-router)
CSS are in .vue directly, into a <style lang="scss">, so if i read doc correctly it's vue-loader who manage lang="scss"
The problem
I had a probleme with mini-css-extract plugin : like many people i get a "conflict order warning". I read a lot and the best way to solve it, it's to re-order css (and so .vue child import into parent .vue).
But i stuck :
I read that not add scoped or module into <style> is not a good practice, but when i had scoped or module it does not change anything.
It's drive me crazy, i don't understand where the order of the component is in conflict. I can give snippet if it's usefull for somebody but app is large and not i'm not sure that i can reproduce error
Thank for any help
The text was updated successfully, but these errors were encountered: