nex3 on main
Fixes typos (#1879) (compare)
nex3 on sync-test
nex3 on main
Update synchronization tests to… (compare)
nex3 on sync-test
Update synchronization tests to… (compare)
nex3 on sync-test
Update synchronization tests to… (compare)
dependabot[bot] on npm_and_yarn
Bump protoc from 1.0.4 to 1.1.3… (compare)
nex3 on sync-test
Update synchronization tests to… (compare)
@import
will be removed in a future version of Sass. as @import
has a different existing use in CSS. Also @use
is a more powerful approach. This also means that it is more complex. But worth learning if starting a new Sass project. What JS framework you use is up to you
Thank you, @TheJaredWilcurt . I think one of the main reasons for advocating the shift to @use is that @import's support will cease in the future. There are indeed other advantages:
Partial vs non-partial
One of the main advantages of partials, as far as I understand, is that they don't transpile into CSS on their own, but only when @imported/@used into a non-partial file. My question is whether this was the only technical difference.
I am not 100% sure, but as far as I understand, you don't have such a problem in angular applications as during build time only specified scss files would be transpiled - here comes my question: if my understanding is correct, is there any other good reason why one would opt for partials instead of non-partials.
@use
).
Hi all, I'm migrating an app from node-sass to dart-sass, moving over from using @imports to @use and so on. I'm wondering if I've understood this correctly...
Previously I could @import all variables from a _config.sass file, and any subsequent sass file would have access to those variables. Now with new sass version, we have scoped variables, so I'll be addressing those variables with something like: config.NEUTRALGRAY
- namespaced.
My question is.. now that @use works more like JS imports, am I supposed to import (@use) this config file containing my variables in every sass file that uses those variables? So basically 2-3 hundred files now need @use "config"
at the top. Is that right?
output.replaceAll('REPLACE', 'Some value');
$var
might be a value used in other Sass logic
.example { font-weight: medium; }
will come out unchanged
.example{color:rgb(255, 255, 255)}
will become .example{color:#fff}
for example. But font-weight: medium;
is just an alias for font-weight: 600
, it shouldn't replace it with 500
color: red
to color: #A00
instead of it's true value #F00
font-weight: 500
just type it that way in your document. It's just CSS, it has nothing to do with Sass
$medium: 500
.example
font-weight: $medium
@TheJaredWilcurt following the MDN font-weight documentation, 500 is medium.
I don't get what you say "font-weight: medium literally translates to font-weight: 600", there is nothing replaced if I SASS a CSS file with "font-weight:medium"
https://developer.mozilla.org/en-US/docs/Web/CSS/font-weight