Sass

The official Sass twitter account. Follow everyone's favorite CSS language for updates, information, and announcements. Mostly run by @nex3.

[Sass @SassCSS]

Sass is more than a technology; it is a welcoming community and we are dedicated to preserving this. Please read & RT http://t.co/X1LAgTLbiJ

[Sass @SassCSS]

We've got a new proposal out for review! This one adds support for analogous sets of color channels, a new concept that just landed in the CSS spec a few weeks ago. It's technically a breaking change, so we'd welcome your feedback! https://t.co/aMufQdBM4D

[Sass @SassCSS]

We have another proposal out for review! This makes adjacent compound selectors that are invalid in CSS, like "[id]a", invalid in Sass too. Let us know what you think! https://t.co/Tjt2id6jQ6

[Sass @SassCSS]

We've got another proposal out for review, this one for the JS API! We're planning to change the sourceMapIncludeSources option to clarify when and how source maps are embedded. Let us know what you think! https://t.co/GKu24oOrip

[Sass @SassCSS]

We've got another proposal out for review, and this one's meaty! It proposes adding Sass support for the new plain CSS if() function in place of Sass's old if() function syntax. Let us know what you think! https://t.co/z9Oa1bgjS9

[Sass @SassCSS]

We have a new language proposal out for review! This adds support for new syntax that's recently landed for the attr() function, which includes one breaking change: user-defined functions can no longer be named "type()". Let us know what you think! https://t.co/gn0C1hD9zM

[Sass @SassCSS]

We've got an exciting new language proposal out for review that adds support for multiline expressions in the indented syntax. Take a look at the explainer at https://t.co/1CcMOl6XjH and let us know what you think!

[Sass @SassCSS]

Thrilled to announce that after years of work, Dart Sass 1.79.0 has been released with support for wide-gamut color spaces! Read all about it in the blog post by Miriam Suzanne https://t.co/F1iQ3FWl8I

[Sass @SassCSS]

@TypeErrorDev For performance reasons, Dart Sass doesn't support customizable precision. You can manually convert a function to a given precision like so : https://t.co/YyyDYT6ycX

[Sass @SassCSS]

@TypeErrorDev Yes, you can call functions within mixins as long as they're in-scope for the current module.

[Sass @SassCSS]

We've got a new language proposal out for review. This one involves a breaking change in the way declarations are handled when interleaved with nested rules, so please take a look: https://t.co/uAsVxVRbjF

[Sass @SassCSS]

We have a new, small proposal out for review. This deprecates mixins and functions beginning with "--" with the intention of making them errors in a future version, to avoid conflicting with plain-CSS functions and mixins. Let us know what you think! https://t.co/68SUYAnNj3

[Sass @SassCSS]

We've got a new proposal out for public review! This one removes the meta.feature-exists() function, which hasn't had any few features added in years. See https://t.co/0Vc9nvuVyL for details, and let us know what you think!

[Sass @SassCSS]

We've got a new proposal out for review! This one adds a JS API for sharing resources between Sass compilations, specifically so embedded host users can get as much performance as possible.

https://t.co/5bwGd9TjH0

[Sass @SassCSS]

Excited to announce that as of Sass 1.69.0, we now support first-class mixins! You can get a mixin as a value with meta.get-mixin(), and invoke it using the new built-in meta.apply() mixin. This allows mixins to be passed into libraries and dynamically invoked.

[Sass @SassCSS]

We've got another language proposal out for review! This one codifies "pkg:" as the URL scheme for Sass packages and adds a built-in loader for npm-style packages. https://t.co/7TO3UsShqF

[Sass @SassCSS]

If you've been following along with our work on support for CSS Colors 4, you may be excited to know that we now have a parallel proposal out for review adding support for new color spaces to the JS API! https://t.co/DydwjsBo7l

[Sass @SassCSS]

We have a new language proposal out for review! This one adds support for first-class mixin objects, similar to first-class functions today. Check it out at https://t.co/MXa8xjqDcb and let us know what you think!

[Sass @SassCSS]

The tradeoff for exposing a color.js Color is that the sass package would need to add it as a dependency. The sass-embedded package would need it as a dependency in either case, since it doesn't have direct access to the Sass compiler's color logic. So what do you prefer?

[Sass @SassCSS]

We're considering some options for exposing CSS color spaces in the JS API. We could just expose each color in its own color space with no support for conversion between them, but that's not very user-friendly. On the other hand, color space conversion logic is complex!

[Sass @SassCSS]

We could lean on the excellent https://t.co/Myvnr0Rav7 library for conversions, but there are two ways that could work. We could either directly expose a color.js Color object for every SassColor, or we could encapsulate its logic in our own custom APIs.