You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to stop using globally defined SCSS variables and instead add an @import/@use in the files that need them. However, right now I think that would mean manually adding those import statements to the top of my files when I reference a variable or mixin.
I would love it if this extension could automatically add those imports for me, in the same way that the JS and TS autosuggests do.
The text was updated successfully, but these errors were encountered:
dkniffin
changed the title
Add support for auto import
Add support for auto import/use
Feb 23, 2021
Sass is deprecating his @import to use @use, now this has some advantages but is a pain in the ass for someone like me that has space variables, color variables, border variables, mixins for responsive, etc.
if i code in modules and components and i code a _hero.scss component i have to import manually all the imports in the sass file that slows me a lot and for every component for every piece of code i have to do this
Now, vscode has an auto import setting you configure it like this
In js, tsx, astro, svelte, etc all these special files have features for auto-importing what you need, this should be added in sass extension also for improve the speed
I'm sad to see this feature request was created in 2021 and no response from the team, 3 years for one of the more important features, and now is more important for what I mentioned above
I would like to stop using globally defined SCSS variables and instead add an
@import
/@use
in the files that need them. However, right now I think that would mean manually adding those import statements to the top of my files when I reference a variable or mixin.I would love it if this extension could automatically add those imports for me, in the same way that the JS and TS autosuggests do.
The text was updated successfully, but these errors were encountered: