![]() Recently, LibSass has become part of the Sass community, and Ruby Sass and LibSass are maintained at the same speed as much as possible. Because LibSass was not directly updated after the releases of Ruby Sass, there were differences between Ruby Sass and LibSass. In the past, the Sass Ruby gem was leading in regards to developing new features. You can read more about Grunt in Chapter 16, Setting up a Build Chain with Grunt, of this book.Īlso, a gulp version for Ruby Sass is available at. You can read more about Foundation in Chapter 11, Foundation and Sass. Bootstrap, as discussed in Chapter 12, Bootstrap and Sass, of this book, uses Grunt, while Foundation uses Gulp. In this book, Gulp is used for setting up build chains without saying that it's better than Grunt or any other task runner. On the other hand, people find streams (saving file contents in memory) more intuitive and the number of Gulp plugins grows fast. Grunt has a longer history and a big community too. Grunt does not use streams like Gulp, but saves results directly in files. Gulp is just like Grunt-a task runner for node. In the Adding Compass to an existing Sass project recipe of Chapter 6, Using Compass, you can read how to integrate Compass into existing projects too. This recipe demonstrates how to set up a project with only Compass. Bourbon is another library of Sass mixins. And in Chapter 13, Meeting the Bourbon Family, of this book you will be acquainted with Bourbon. In Chapter 9, Building grid-based layouts with Sass, and Chapter 10, Susy and Sass, of this book, you can read about Susy. Susy was originally built to be a part of the Compass ecosystem. Susy is a powerful set of Sass mixins for building grid-based layouts. Many other frameworks for Sass are available too. For more information on integrating compass in your compile process, you can read Chapter 6, Using Compass.Ĭompass is a widely used Sass framework. You can also directly use the features, mixins, and helper functions of Compass together with the command-line Sass compiler (see the Using Sass on the command line recipe of this chapter) by setting the -compass option. You can write your SCSS code in your favorite text editor, but at the end of this chapter, you will also be introduced to some Graphical User Interfaces ( GUI) that will help you write and compile your code more easily. ![]() In this book, the SCSS syntax for Sass has been used in favor of the original indented Sass, that is, the Ruby-like syntax. Together with a task runner, such as Gulp or Grunt, you can use the sass-node to set up a build chain for your projects. ![]() The sass-node is an interpreter of LibSass for Node.js, and it enables you to compile Sass in a Node.js environment. LibSass is a C/C++ port of the Sass engine.īased on LibSass, sass.js is a pure JavaScript implementation of the Sass engine, which enables you to compile Sass code with JavaScript and run sass.js in your browser. You will not only learn how to use Sass using the command line interface ( CLI), but you will also be introduced to LibSass. Var prefixer = postcss() Ĭleaner.process(css).This chapter guides you through the installation of Sass and explains the different ways you can compile your Sass code into static CSS. Write your CSS rules without vendor prefixes (in fact, forget about themĪutoprefixer will use the data based on current browser popularity and property It is recommended by Google and used in Twitter and Taobao. PostCSS plugin to parse CSS and add vendor prefixes to CSS rules using valuesįrom Can I Use.
0 Comments
Leave a Reply. |