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.

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!

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 and let us know what you think!.

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

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:

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!

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 for details, and let us know what you think!.

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.

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.

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.

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!

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 and let us know what you think!.

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?.

We could lean on the excellent 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.

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!.

We're excited to officially announce Dart Sass support for running as a JS library in the browser, and with it a new Sass Playground!

Looks like we're all set now. Thanks for your patience!.

We're switching hosting providers for which means we need to provision a new SSL certificate. If you see HTTPS errors, please bear with us for now, they shouldn't last more than a day!.

Do you maintain a host wrapper for the Embedded Sass Protocol? If so, we've got some changes coming that we want your feedback on!

Another proposal as well: this one just changes the way loud comments are ordered with use and forward to better match user expectations.

If you maintain a Sass plugin for a build system, this is definitely one to take a look at. It's designed to make those easier to upgrade to the new JS API.