Great! Yeah that is always the case for me, I always have sort of base styles that apply globally, but I want to scope all my components. So doing it this way works perfectly :)
Hi Emmanuel, the import.scss file should just have things like variables and mixins that the other files will need access to. If you don't use the plugin to serve the variables etc, you can't access them and use them within other components.
Great! Yeah that is always the case for me, I always have sort of base styles that apply globally, but I want to scope all my components. So doing it this way works perfectly :)
Hey Allan and Lynne, Sorry, kinda lost here :) Can you explain what you did to solve this? Especially with the
import.scss
fileAlthough, I think maybe importing the
global.scss
file inApp.vue
might also be a good solution?Hi Emmanuel, the import.scss file should just have things like variables and mixins that the other files will need access to. If you don't use the plugin to serve the variables etc, you can't access them and use them within other components.
So basically, from your example. Everything imported in the
global.scss
file is available to use in all the components?Awesome post Lynne. This helped me clean up way too many double imports.
Emmanuel, I was a little confused too.
For the stylesheet that you call into
vue.config.js
only importmixins
andvariables
(no style selectors/rules).Call other
global.scss
(declared rules and stuff) elsewhere, likemain.js
or a parent app likeApp.vue
.Any style rules imported to a stylesheet through
vue.config.js
will import again for each component that uses it.