nex3 on color-spaces
nex3 on feature.color-4
Fix some bugs in `color.complem… (compare)
nex3 on color-spaces
Be strict about whitespace in c… Delete dev dependency on Sass w… Implement string.split() (#1839… and 11 more (compare)
nex3 on main
Add all CSS length units in kno… (compare)
dependabot[bot] on npm_and_yarn
jathak on update-jest
Also update ts-jest (compare)
jathak on update-jest
Bump jest and @types/jest to la… (compare)
nex3 on main
fix typo in `@extend` spec (#34… (compare)
@TheJaredWilcurt
that's about as minimum as I've been able to get with my setup, and still have Bootstrap involved; sure, likely can be reduced with some fussing around.
are you suggesting that
test.scss
:root {
--some-css-var: sass-namespace-name.sass-function-name("argument");
}
SHOULD work on compile?
Or is that the question you're suggesting the minrepro to find out?
@charset "utf-8"
Hello everyone!
I made something for Sass projects which I think could be useful to others :)
Sass currently doesn’t have up-to-date linter or error reporter, so I wanted to integrate it with current industry standard linter (Stylelint), so I made plugin which reports Sass errors and depractions as linter errors: https://github.com/niksy/stylelint-sass-render-errors
It’s based on other tool which is used to extract those information from Sass rendering process: https://github.com/niksy/sass-render-errors
Besides reporting errors and deprecations from render result, it can (optionally) check for undefined functions based on current native CSS functions.
Hope this helps you and others in better project maintenance :)
And, as always, suggestions are welcome! :)
My project Uniform CSS has also officially launched as well! This project is a fully customizable utility generator and CSS framework for Sass to compete against Tachyon, BassCSS, and Tailwind!
Apart from having full control over how you can generate utility classes, it has other cool features like, API Functions, Apply support, JSON Reference output mode, and multi-property custom utility support. Please check it out: https://uniformcss.com
It's still in proposal state, yeah, it looks like it gets processed correctly in both LibSass and DartSass
INPUT:
.sidebar
container-type: inline-size
container-name: sidebar
@container sidebar (min-width: 700px)
.card
display: grid
grid-template-columns: 2fr 1fr
OUTPUT:
.sidebar {
container-type: inline-size;
container-name: sidebar;
}
@container sidebar (min-width: 700px) {
.card {
display: grid;
grid-template-columns: 2fr 1fr;
}
}