A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
Hey Allan and Lynne, Sorry, kinda lost here :) Can you explain what you did to solve this? Especially with the import.scss file
import.scss
Although, I think maybe importing the global.scss file in App.vue might also be a good solution?
global.scss
App.vue
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 import mixins and variables (no style selectors/rules).
vue.config.js
mixins
variables
Call other global.scss (declared rules and stuff) elsewhere, like main.js or a parent app like App.vue.
main.js
Any style rules imported to a stylesheet through vue.config.js will import again for each component that uses it.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
Where hackers, sticks, weekend warriors, pros, architects and wannabes come together
Hey Allan and Lynne, Sorry, kinda lost here :) Can you explain what you did to solve this? Especially with the
import.scssfileAlthough, I think maybe importing the
global.scssfile inApp.vuemight 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.scssfile 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.jsonly importmixinsandvariables(no style selectors/rules).Call other
global.scss(declared rules and stuff) elsewhere, likemain.jsor a parent app likeApp.vue.Any style rules imported to a stylesheet through
vue.config.jswill import again for each component that uses it.