Sass Blog

Page 7 of 9

Previous page

  • Sass 3.5 is Released

    Posted 7 July 2017 by Natalie Weizenbaum

    I’m excited to announce that I’ve just released the stable version of Sass 3.5. This release focuses on compatibility with new CSS syntax, and helps lay the groundwork for the upcoming module system and compatibility with Dart Sass.

    Most of the major features in 3.5 were already in the release candidate, which you can read about here. But there are a handful of other changes that have been added since then:

    • Sass now supports the the ::slotted() pseudo-element, including extending its selector arguments.

    • The var() function may be safely passed to the CSS color functions rgb(), rgba(), hsl(), and hsla().

    • Transparent colors created by Sass’s color functions will now be written as rgba(0, 0, 0, 0) rather than transparent to work around a bug in Internet Explorer. Colors written as transparent in the document will still be emitted as written.

    Dart Sass CompatibilityDart Sass Compatibility permalink

    I wrote last month about our plans for keeping Ruby Sass compatible with Dart Sass in…

  • Dart Sass is in Beta

    Posted 5 June 2017 by Natalie Weizenbaum

    Last weekend was three days long and the weather in Seattle was gorgeous. Contrary to stereotype, spring here is often characterized by bright sunny days that aren’t too hot, and on days like that I love to curl up on the armchair in my living room and write some code. This weekend, that meant finishing up the last few outstanding @extend bugs, finally making Dart Sass fully sass-spec compatible[1].

    This is the milestone we’ve decided would mark the transition from alpha to beta releases of Dart Sass. Dart Sass 1.0.0-beta.1 is up now on npm, pub, and Chocolatey, and I encourage people to start trying it out in their own applications. We’ve fixed all the bugs we know about, so now we need our diligent users to find the rest of them and tell us!

    Next Steps: Ruby SassNext Steps: Ruby Sass permalink

    There are a number of intentional behavior differences between Dart Sass and the existing implementations. All of these differences are things we think…

  • Sass and Browser Compatibility

    Posted 11 February 2017 by Natalie Weizenbaum

    One of the core design principles of Sass has always been to understand CSS as little as possible. As a CSS preprocessor of course we have to understand the syntax of CSS, but as much as we can we try to avoid caring about the semantics—the meaning behind the styles. This means that Sass has no idea which properties are valid, which HTML elements actually exist, or even to a large extent what the syntax of most @-rules is.

    We get a lot of benefit from this. The less built-in knowledge Sass has about CSS, the less likely it is to work poorly with new CSS features. Imagine having to file a feature request every time you want to use a new CSS property—that would suck! Instead, older versions of Sass will happily keep working unless the actual syntax changes, which is much rarer.

    Because of this decoupling, we’ve never needed to worry much about browser compatibility. Sass just passes whatever CSS its given on through. It’s up…

  • Dart Sass is On Chocolatey

    Posted 13 January 2017 by Natalie Weizenbaum

    One of the quieter benefits of moving to Dart is how easy it is to distribute Dart applications. The Dart VM is able to bundle all the sources for an application into one easy-to-load binary snapshot, which means running a Dart application requires only three files: the dart executable, the snapshot file, and a tiny shell script to invoke the app[1]. This is a huge relief coming from Ruby, which required a whole installation of executables and libraries in order to run a single app.

    Those three files are what we distribute today on our GitHub release page. But finding, downloading, and opening an archive and adding it to the command-line path is still a barrier to entry that we’d like to avoid where possible. Today we’re taking a step in that direction by releasing a Dart Sass package on Chocolatey, the Windows package manager. You can install it now using:

    $ choco install sass -prerelease

    This will give you a sass executable that runs Dart…

  • Announcing Dart Sass

    Posted 31 October 2016 by Natalie Weizenbaum

    Over the past few months, I’ve been quietly working on a new project. Today I’m ready to announce Dart Sass to the world. It’s a totally new implementation of Sass, designed to be fast, easy to install, and easy to hack on. It’s not yet complete—I’m steadily working my way through sass-spec—so today I’m just releasing version 1.0.0-alpha.1. But it’s solid enough for you to download, play with, and start filing issues.

    You can download a standalone archive from the release page—just extract it, add the folder to your path, and run dart-sass. Dart also compiles to JavaScript, so if you have npm installed you can install the JS version by running npm install -g dart-sass. And, if you happen to be a Dart user yourself, you can install it using pub global install sass.

    Why Rewrite Sass?Why Rewrite Sass? permalink

    Over the past few years, there have been two primary implementations of Sass. Ruby Sass was the original, written mostly by me…

Next page