Page 1 of 7
Posted 1 February 2022 by Natalie Weizenbaum
After several years of planning and development, I’m excited to finally announce the stable release of Embedded Dart Sass along with its first official wrapper, the
sass-embedded package available now on npm!
Embedded Sass is an ongoing effort to make a highly-performant Sass library available to as many different languages as possible, starting with Node.js. Although Node.js already has access to the pure-JS
sass-embedded to be a major boon to developers for whom compilation speed is a concern, particularly the remaining users of
node-sass for whom performance has been a major reason to avoid Dart Sass.
sass-embedded package fully supports the new JS API as well as the legacy API other than a few cosmetic options. You can use it as a drop-in replacement for the
sass package, and it should work with all the same build plugins…
Posted 21 November 2021 by Natalie Weizenbaum
Because this is such a substantial addition, we want to give users a chance to kick the tires a bit before we set it in stone, so we’ve released it as a release candidate in Dart Sass 1.45.0-rc.1. Download it, try it out, and let us know what you think by filing issues or sending us a tweet. Unless major changes are necessary, we plan to make a stable release some time next week.
The new API comes with four new entrypoint functions:
compileAsync() take Sass file paths and return the result of compiling them to CSS, while
compileStringAsync() take a string of Sass source and compile it to CSS. Unlike the old API, the async functions all return
Posted 5 August 2021 by Natalie Weizenbaum
The API has four main components, all of which I’ll cover in this post:
As you read on, remember that this API is still just a proposal. We want to hear from you, our users, whether it meets your needs and how we can improve it before we lock it in to a full release. So go ahead and make your voices known on the issue tracker!
node-sass package, which wrapped the now-deprecated
Posted 26 March 2021 by Natalie Weizenbaum
We have recently received the unfortunate but not entirely surprising news that the
node-fibers to improve the performance of the asynchronous
render() method, but going forward this will unfortunately no longer be an option in Node 16 and on.
There are a number of alternative options for reclaiming this lost performance, some of them which are available today, some which are in development, and some which are theoretical but could be made real with pull requests from users like you. Sadly, none of the options that are ready today are drop-in solutions with the same level of ease-of-use as
node-fibers, so if that performance is crucial to you we recommend staying on Node 14 for the time being.
In order to understand how we got here, it’s important to know two pieces of history…
Posted 15 March 2021 by Natalie Weizenbaum
One of the absolutely most-requested features in Sass is the ability to more easily work with
calc() expressions. These expressions have historically been parsed opaquely: between the parentheses, you can put any text at all, and Sass will just treat it as an unquoted string. This has simplified Sass’s parser, since we don’t have to support the specific
calc() microsyntax, and it’s meant that we automatically support new features like the use of CSS variables within
However, it comes at a substantial usability cost as well. Because each
calc() is totally opaque to Sass’s parser, users can’t simply use Sass variables in place of values; they have to interpolate variables explicitly. And once a
calc() expression has been created, there’s no way to manipulate it with Sass the way you can manipulate a plain number.
We’re looking to change that with a new proposal we call “First-Class Calc”. This proposal changes
calc() (and other supported mathematical functions) from being parsed…