Blob Blame History Raw
LibSass - Sass compiler written in C++

Currently maintained by Marcel Greter ([@mgreter]) and Michael Mifsud ([@xzyfer])  
Originally created by Aaron Leung ([@akhleung]) and Hampton Catlin ([@hcatlin])

[![Unix CI](]( "Travis CI")
[![Windows CI](]( "Appveyor CI")
[![Coverage Status](]( "Code coverage of spec tests")
[![Percentage of issues still open](]( "Percentage of issues still open")
[![Average time to resolve an issue](]( "Average time to resolve an issue")
[![Bountysource](]( "Bountysource")
[![Join us](]( "Slack communication channels")

[LibSass]( "LibSass GitHub Project") is just a library!
If you want to use LibSass to compile Sass, you need an implementer. Some
implementations are only bindings into other programming languages. But most also
ship with a command line interface (CLI) you can use directly. There is also
[SassC](, which is the official lightweight
CLI tool built by the same people as LibSass.

### Excerpt of "sanctioned" implementations:

- (Node.js)
- (Perl)
- (Go)
- (Ruby)
- (C#)
- (JS)
- (Python)

This list does not say anything about the quality of either the listed or not listed [implementations](docs/!  
The authors of the listed projects above are just known to work regularly together with LibSass developers.


LibSass is a C++ port of the original Ruby Sass CSS compiler with a [C API](docs/
We coded LibSass with portability and efficiency in mind. You can expect LibSass to be a lot
faster than Ruby Sass and on par or faster than the best alternative CSS compilers around.


As noted above, the LibSass repository does not contain any binaries or other way to execute
LibSass. Therefore, you need an implementer to develop LibSass. Easiest is to start with
the official [SassC]( CLI wrapper. It is *guaranteed* to compile
with the latest code in LibSass master, since it is also used in the CI process. There is no
limitation here, as you may use any other LibSass implementer to test your LibSass branch!


Since LibSass is a pure library, tests are run through the [Sass-Spec](
project using the [SassC]( CLI wrapper. To run the tests against LibSass while
developing, you can run `./script/spec`. This will clone SassC and Sass-Spec under the project folder and
then run the Sass-Spec test suite. You may want to update the clones to ensure you have the latest version.
Note that the scripts in the `./script` folder are mainly intended for our CI needs.


To build LibSass you need GCC 4.6+ or Clang/LLVM. If your OS is older, you may need to upgrade
them first (or install clang as an alternative). On Windows, you need MinGW with GCC 4.6+ or VS 2013
Update 4+. It is also possible to build LibSass with Clang/LLVM on Windows with various build chains
and/or command line interpreters.

See the [build docs for further instructions](docs/!


Current LibSass 3.4 should be compatible with Sass 3.4. Please refer to the [sass compatibility
page]( for a more detailed comparison. But note that there
are still a few incomplete edges which we are aware of. Otherwise LibSass has reached a good level
of stability, thanks to our ever growing [Sass-Spec test suite](

About Sass

Sass is a CSS pre-processor language to add on exciting, new, awesome features to CSS. Sass was
the first language of its kind and by far the most mature and up to date codebase.

Sass was originally conceived of by the co-creator of this library, Hampton Catlin ([@hcatlin]).
Most of the language has been the result of years of work by Natalie Weizenbaum ([@nex3]) and
Chris Eppstein ([@chriseppstein]).

For more information about Sass itself, please visit

Initial development of LibSass by Aaron Leung and Hampton Catlin was supported by [Moovweb](


Our [MIT license](LICENSE) is designed to be as simple and liberal as possible.