Best practise @use @forward for deeply nested folder structure?
In a large C#/Blazor Wasm code base and a deeply nested sass folder structure, what is the best approach when transitioning from @import to @forward and @use?
Working with Sass in a Blazor Wasm app the main.scss needs to reside outside the sass folder, because of the set up we have for sass:watch. We can call it global-main.scss.
From the global-main.Scss there are then two other files (one for each project) that imports this global-main.
Working with Sass in a Blazor Wasm app the main.scss needs to reside outside the sass folder, because of the set up we have for sass:watch. We can call it global-main.scss.
From the global-main.Scss there are then two other files (one for each project) that imports this global-main.
A friendly place for developers to meet other devs, ask questions, get help, and just have a good time 🙂.
36,263Members
Resources
Similar Threads
Was this page helpful?
