v3.3.2

This release fixes an issue that was causing segfaults when using Node Sass with some other native modules like fsevents. This issue caused to revoke the v3.3.0 and v.3.3.1 npm packages whilst we figured out a solution. (#1107)

Big thanks to everyone who reported the issue and helped @saper and @xzyfer debug it.
Big thanks to the @kkoopa and @bnoordhuis for a speedily releasing nan@2.0.8.

v3.3.1

This release works arounds a segfault that occurs when Node Sass is used with fsevents@0.3.8.

Changelog

Bug fixes

• Workaround incompatibility with fsevents@0.3.8 (@xzyfer, #1107 (comment))

v3.3.0

The Node Sass team is happy release v3.3.0. This release has been a long time coming, and for good reason.

With the release the of a new major io.js release we decided to spend some time working on our development infrastructure. The hope is that we now have the ground work in places to more rapidly respond to new runtime versions.

News

The Node Sass team is super excited to welcome long time contributor @saper to the team!

Changelog

io.js v3 support

Thanks to a massive effort from @saper and @kkoopa we update to nan@2 which gave us io.js v3 compatibility.
This was the major hold up for this release.

This closes #1086, #1085, #1082, #1073, #1071, #1067, #1064, #1059, #1053

Let this be a reminder to always search before opening a new issue.

CI improvements

@am11 @saper and @xzyfer implements various stability and speed improvements to our CI process. This will enable us to produced more frequent release.

• Speed: use cached npm and gyp files between builds (@saper, #1099)
• Stability: test explicit Windows runtime versions (@am11, #1097)
• Stability: test explicit Linux and OSX runtime versions (@xzyfer, #1096)
• Stability: don't launch npm in PowerShell (@am11 @saper, #966)
• Stability: migrate test coverage reporting to instanbul (@saper, #910)
• Stability: increased test coverage to low level APIs (@saper, #1058)

Minor features

• Update npm dependencies (@am11, #1033)

Document updates

• Llink to LibSass repository (@cydrobolt, #1094)
• Clearer explanation of the outFile option (@gpapin, #1084)
• Clearer explanation of the indentedSyntax option (@dkebler, #1081)
• Locate pangyp via module API (@saper, #1063)
• Improve troubleshooting docs for Windows (@saper, #1060)
• Remove obsolete note for io.js on Windows (@am11, #1033)
• Document gotcha for VS2015 task runner (@amm, #1033)
• Remove stray comma (@JAFong, #1028)
• Fix typo (@lencioni, #1020)

Bug fixes

• Watcher wasn't watching transitive dependencies for .sass files (@xzyfer, #1075)

Thanks!

We'd like to say a huge thanks! to everyone above who helped make this release possible, as well as everyone who opened issues (even all the duplicates).

Honourable mentions to @kkoopa and @saper for all their hard work the io.js v3 compatibility.

v3.2.0

This release bumps Libsass to 3.2.5 which brings with it a bunch of fixes. Check the changelog.

Features

• Updated Libsass to 3.2.5 (@xzyfer, #992)

v3.1.2

Fixes

• Fixed multi-file compilation sometimes writing to wrong file (#967, @kkopachev)
• Fixed multi-file compilation missing source maps (#903, @am11)

Notes

The source-map option accepts true as value, in which case it replaces destination extension with .css.map. It also accepts path to .map file and even path to the desired directory. In case of multi-file compilation path to .map yields error.

v3.1.1

Fixes

• Fixed ability to watch whole directory (#952, @kkopachev)

v3.1.0

This release addresses some minor issues in the recent v3.0.0 release, as well documentation updates.

We've also included not one, but two Libsass updates! 🎉

Features

• Updated to Libsass 3.2.4 the release notes for 3.2.3 and 3.2.4

Fixes

• Fixed Windows install issues (@saper @xzyfer, #945)
• Fixed usage of reserved word package (@ajp427, #936)
• Fixed segmentation fault with bootstrap 3 (@xzyfer, #950)
• Fixed some missing CLI usage instructions (@akauppi , #928)

Documentation

• Libsass now supports all output types (@antleblanc, #940)

Thanks !

Big thank you to all our contributors, and to everyone who opened issues. Honourable mentions to @ajp427, @akauppi, @am11, @antleblanc, @saper and @xzyfer.

v3.0.0

The node-sass team is excited to release the long awaited v3.0.0!

This release has been a massive undertaking by the node-sass team and our many contributors!

News

This release marks two major events for node-sass.

Firstly, this the most significant release to date, and includes the largest Libsass release to date. Do yourself a favour and check out the massive Libsass 3.2.0 changelog.

Secondly, @xzyfer has been promoted to project lead. We all owe @am11 a "thank-you" for all his hard work making node-sass an incredible success. I can only hope to do as good of a job - You can read more in #864.

Changelog

Breaking Changes

• Use node-style callbacks rather than object properties - @jakobo
• API throws Error object instead of Strings - @am11, @sindresorhus
  Old:

require('node-sass').render({
  /* options */,
  success: function (result) { },
  error: function(err) {
    assert(typeof err === 'string');
  }
});

New:

require('node-sass').render({
  /* options */
}, function (err, result) { 
  if (err) {
    assert(err instanceof Error);
  }
});

• API returns Buffer output as opposed to String - @am11
• Remove image path options which are no longer supported by Libsass - @am11
• SourceMap path configurations resolved against cwd - @am11
• CLI defaults to stdout - @am11, @xzyfer
• CLI --watch flag is now boolean - @wesleytodd

Features

• Update to Libsass 3.2.2 - @xzyfer
• Add sourceMapRoot option - @am11
• Configurable linefeed - @am11, @matryo
• Default --recursive flag to true - @wesleytodd
• Improved watcher - @xzyfer
• Expose this.options to importer and render callbacks - @jakobo
• Binaries downloadable from custom URL - @am11, @johnrc, @saper
• Binaries are now uploaded as release assets via SASS_BINARY_SITE- @am11, @nschonni
• Set User-Agent HTTP header when fetching binaries - @saper
• Improved support for git-backed installation - @xzyfer

Experimental features

• Add support for custom importers - @am11
• Add support for custom functions - @matryo

Documentation

• README formatting fixes - @tomfuertes
• Fixes publish issues with Windows - @am11, @mgreter
• Created a troubleshooting guide - @xzyfer

Fixes

• Better support for io.js rapid release cycle - @am11, @xzyfer
• More reliable installation and Libsass compilation - @saper, @am11
• Kill watcher processes during test - @saper
• Improved error handling when fetching binaries - @saper

Known issues

• Custom importer hangs the process if too many files are imported (#857)

Thanks!

This release wouldn't be possible without the hard work of @am11, @andyshora, @danielstjules, @jakobo, @kevva, @matryo, @paulcpederson, @saper, @tomfuertes, @wesleytodd and @xzyfer.

v3.0.0 third beta

This is the 3.0.0-beta.7 release.

News

With this release the I (@xzyfer) have become the new project lead for node-sass. I want to thank @am11 and the previous projects for their incredible work making node-sass what it is. I can only hope to do their work justice.

Installation

npm install node-sass@beta

Changelog

Libsass

We've updated to latest libSass release.

Check out the 3.0.0-beta.6 changelog for more information.

Features

• updated to libSass 3.2.0-beta.6 (@xzyfer, #872)
• added a --quiet CLI flag (@paulcpederson, #841)
• added globbing support to the CLI (@paulcpederson, #828)
• improved documentation for experimental custom importers (@am11, #697)
• init libSass submodule when npm installing via git url (@xzyfer, #874)

Bug fixed

• libuv segfaults with render (@saper, #713)
• typo in console output (@saper, #856)
• linting error (@andyshora, #842)
• improved error handling with outFile (@am11, #839)
• improved error handling for experimental custom importers (@am11, #837)

Known issues

• custom importer hangs the process if too many files are imported (#857)
• installation fails on Windows with iojs due to upstream issue (#870)

Thanks!

This release wouldn't be possible without the hard work of @am11, @andyshora, @paulcpederson, @saper, and @xzyfer.

v3.0.0 third beta

This release has been removed from npm due to release issue.

This has been superseded by v3.0.0-beta.7