ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Libsass Build

by blitzrk ST2/ST3

Build system for Sass/scss files in Sublime Text 2/3 with no external dependencies

Labels sass, scss, css

Details

Installs

  • Total 6K
  • Win 4K
  • OS X 2K
  • Linux 543
Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23 Dec 22 Dec 21 Dec 20 Dec 19 Dec 18 Dec 17 Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11 Dec 10
Windows 0 3 6 4 3 0 3 5 5 2 1 2 2 7 5 6 4 1 3 2 2 4 6 0 0 0 4 5 5 6 5 0 2 6 4 4 7 8 2 1 2 7 6 8 0 4
OS X 0 3 1 0 0 1 3 5 4 2 0 1 1 3 1 4 5 1 1 2 0 1 3 0 0 1 1 1 2 1 0 1 0 2 1 1 3 6 1 0 1 1 4 1 0 2
Linux 0 1 2 2 0 0 0 2 2 0 0 0 1 0 0 1 2 1 0 0 0 1 1 1 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 0 2 4 1 1 0

Readme

Source
raw.​githubusercontent.​com

Libsass versionSassc version

Libsass Build

Linux & OSX Windows
Build Status ?

Build system for Sass/scss files in Sublime Text 2/3 with no external dependencies

It uses libsass (via the official sassc front-end) for faster compile times compared to the official Ruby implementation.

https://github.com/blitzrk/sublime_libsass

Configuration

By default, sassc is given no arguments and css files are put in build/css relative to the assumed root of the project (the outermost parent directory containing a sass file from the file being compiled). The default output directory and sassc flags can be modified Preferences->Package Settings->Libsass Build ->Settings - User. There is a skeleton in Settings - Default or see below.

A project-specific configuration can written to .libsass.json file. Additionally, the location of this file will make explicit the root of the project as far as where sass imports and the output directory is based. You can edit this config or generate an example by selecting the menu item Tools->Libsass Build ->Edit Project Config.

Example:

You have the directory structure:

/path/to/projects/example/
|-- lib/
|-- static/
|   |-- js/
|   |-- css/
|   |   +-- main.css
|   +-- images/
|-- .libsass.json
+-- styles/
    |-- partials/
    |   +-- _reset.scss
    +-- main.scss (has @import 'partials/reset';)

Then you could use:

/path/to/projects/example/.libsass.json:

{
    "output": {
        "dir": "static/css",
        "structure": "flat"
    },
    "compile": {
        "line-comments": true,
        "line-numbers":  true,
        "style":         "nested", // Comments allowed in `.libsass.json`, but not `*.sublime-settings`
        "load-path":     "/path/to/projects/example/styles" // You DO NOT need this line
    }
}

or alternatively in /path/to/projects/example/styles/.libsass.json:

{
    "output": {
        "dir": "../static/css", // This path gets normalized, so `..`s get handled
        "structure": "flat"
    },
    "compile": {
        "line-comments": true,
        "line-numbers":  true,
        "style":         "nested",
        "load-path":     "/path/to/node_modules/bourbon" // Get your fill of bourbon or point to compass!
    }
}

Structure

In config you can specify in output.structure whether you want your compiled assets to be side-by-side or nested in their original structure.

./
|-- .libsass.json (output dir is "css")
|-- css/
+-- scss/
    |-- main.scss
    +-- modules/
        +-- menu.scss
  • nested (default): compiles to css/scss/main.css and css/scss/modules/window.css
  • nested with root directory: if your .libsass.json is further away, remove prefix to nested path
    • ex. “structure”: [“nested”, “scss”]
    • compiles to css/main.css and css/modules/menu.css
  • flat: compiles side-by-side to css/main.css and css/menu.css

Usage

Configuration is entirely optional, so in the simplest case, simply build with Ctrl+Shift+B. If you have another Sass build system installed, you may need to select Sass (libsass) in Sublime's menu.

Troubleshooting

Libsass isn't automatically chosen as the build system

If you have another Sass build system installed, it may be conflicting. If no build system is selected, then you may not have a Sass syntax definition installed or it may be oddly defined (i.e. not using source.sass or source.scss). Try replacing it with another syntax highlighting package such as Sass.

My file compiled, but I don't know where it went!

Libsass looks up the directory structure until it finds (or doesn't find) a .libsass.json config file. If you're not using a config file, then check that there isn't a config in any parent directory. E.g. if you have your project in /home/ben/projects/app and an extraneous config file /home/ben/projects/.libsass.json, the css will output relative to /home/ben/projects instead of to /home/ben/projects/app/build/css.

My configuration doesn't seem to do anything

In version 0.9.0 the configuration format was changed. Sorry about that, but it was important! And hopefully now the names are less confusing, too. Anyway, check out the examples above. The top-level keys are now “output” and “compile” instead of “output_dir” and “options”.

Invalid UTF-8

At the moment there are some bugs in Libsass Sublime's unicode support, so if you see a UTF error, you likely have a non-ascii character in the path or name of one of your files in your project. For now, the best workaround is to just rename your file or directory. This is obviously annoying and it will be fixed as soon as possible.