You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 20, 2019. It is now read-only.
A new version was just released of node-sass, so Doppins
has upgraded your project's dependency ranges.
Make sure that it doesn't break anything, and happy merging!
Upgraded node-sass from 2.1.1 to 3.8.0
Changelog:
Version 3.8.0
Features
Add an audible cue when there's a CLI error behind a --error-bell CLI flag (@Peterhactch, #1578)
Replace cross-spawn-async with cross-spawn (@danez, #1563)
Let watcher know when files are added or removed (@xzyfer, #1538)
Add missing jsdoc for public API functions (@nschonni, #1528)
Add a changelog (@xzyfer, #1523)
Add Node.js 6 support to readme (@coderbyheart, #1506)
Fixes
Fix code coverage reporting (@nschonni, #1583)
Fix the options object passed to render and renderSync being mutated (@xzyfer, #1168)
Version 3.7.0
Node.js 6 support
You've asked, and asked, and asked... and here it is. It took a little longer than we'd hoped due a bug we discovered (https://github.com/nodejs/node/issues/6500) in Node.js 6 which broken our Windows builds.
Previous versions of Node Sass worked fine with Node.js 6 but produced scary looking warnings the console.
Work around Node.js 6 bug in Windows CI (@saper, #1514)
Currently to detect user local settings, when downloading the precompiled binaries, we use a deprecated package. We've replaced this packaged with the offical npm environment variables. This drastically simplifies our install script.
Big thanks to @delitescere! (#1333)
Fixes
Drastically simply we switch Node versions in Travis (@xzyfer, #1500)
Better error message when installing on an unsupported environments (@nschonni@xzyfer, #1487#1491)
Update TODO URL in install error (@nschonni, #1488)
Add Node.js 6 to CI (@nschonni, #1486)
Supported Environments
OS
Architecture
Node
Windows
x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
OSX
x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
Linux
x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
FreeBSD
i386 & amd64
0.10, 0.12, 1, 2, 3, 4, 5, 6
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.6.0
LibSass
We've bumped LibSass to 3.3.6 Herbie (https://github.com/sass/libsass/releases/tag/3.3.6)
Fixes
Segfualt when used with materialize-css (#1464)
Support Environments
OS
Node
Windows x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
OSX x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
Linux x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
FreeBSD x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.5.3
Fixes
Proxies not always being respected when downloading binaries (@xzyfer)
Support Environments
OS
Node
Windows x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
OSX x64
0.10, 0.12, 1, 2, 3, 4, 5
Linux x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
FreeBSD x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.5.2
Fixes
Proxies not always being respected when downloading binaries (@xzyfer)
Support Environments
OS
Node
Windows x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
OSX x64
0.10, 0.12, 1, 2, 3, 4, 5
Linux x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
FreeBSD x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.5.1
Deprecation
A previously undocumented process.sass has been deprecated (#1427). It will be removed in a future release. Access this API will produce a deprecation warning in the console.
LibSass 3.3.5
This release includes the recent massive Delorean release as well as couple follow up bug fix release. We delayed this release until LibSass had fixed some issue that cropped in Delorean.
3.3.5: General Lee (https://github.com/sass/libsass/releases/tag/3.3.5)
Improved installation errors
"The libsass binding was not found.”
Say goodbye to this infamous error. The root cause is unavoidable but we can do a better job and helping you fix it without filing an issue. Thanks to @xzyfer you'll now encounter something a bit more friendly!
Node Sass does not yet support your current environment: OS X 64-bit with Node.js 4.x
For more information on which environments are supported please see:
http://....
Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 4.x
Found bindings for the following environments:
OS X 64-bit with io.js 3.x
OS X 64-bit with Node.js 5.x
This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass to build the binding for your current environment.
Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 4.x
This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass to build the binding for your current environment.
Custom functions
Thanks to @eoneill custom functions now have access to current render context via this.
The benefit of this is that custom functions can persist data (be stateful), for the lifespan of the render. For example this is now possible:
Added bugs url to package.json (@keithamus, #1367)
Thanks!
As always the Node Sass would love to give a huge "thank you!" to all the contributors that made this release possible! We couldn't do it without you. ❤️ ❤️ ❤️
Support Environments
OS
Node
Windows x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
OSX x64
0.10, 0.12, 1, 2, 3, 4, 5
Linux x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
FreeBSD x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.5.0-beta.1
We're releasing this beta for the upcoming v3.5.0 release because of the LibSass bump. Please test this out and file any issue with Sass compilation.
LibSass
We've bumped LibSass to Delorean, check their changelog (https://github.com/sass/libsass/releases/tag/3.3.3) for the juicy details.
Windows XP support
In v3.4.2 LibSass and Node Sass starting compiling our prebuilt binaries with Visual Studio 2015 which caused issues for Windows XP users. After some incredible debugging and investigation by @am11 and @saper we believe we have addressed the Window XP runtime errors.
Features
Updates to contributing documentation (@JohnAlbin, #1264)
Improvements to V8 error handling (@saper, #1309)
Improvements to custom import test coverage (@xzyfer, #1319)
Replace request with got (@zckrs, #1358)
Provide Program Database files (.PDB) for better debugging on Windows (@saper, #1337)
Fixes
Normalize the way of writing 'LibSass' in documentation (@raithit, #1266)
Fix broken URLs in readme (@ReadmeCritic, #1287)
Use https rather than git to check out LibSass in fallback compilation (@saper, #1301)
Fix poor reporting on for failing tests (@saper, #1307)
Fix discrepancy between sync and async importers when returning sass.NULL (@saper, #1296)
Fix error when outputting to a symlinked directory (@nibblebot, #1212)
Fix node executable discovery in build script (@saper, #1323)
Fix detection of Sass spec error specs (@xzyfer, #1342)
Compile against Visual Studio 2015 (@xzyfer, #1248)
Fixes
Disable some flakey tests that are scaring contributors (@xzyfer, #1260#1261)
Fix typos in read me (@ggamel, #1252)
Fix lint errors (@jameslnewell, #1223)
Fix regression in custom importer previous file path (@chriseppstein, #1220)
Add missing tests (@jameslnewell, #1219)
Fix the logo in the read me being too large (@esr360, @1218)
Thanks
A big thanks to everyone who took the time report issues.
The LibSass team (@hcatlin, @mgreter, @saper, @xzyfer) couldn't do this without your help.
Support Environments
OS
Node
Windows x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
OSX x64
0.10, 0.12, 1, 2, 3, 4, 5
Linux x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
FreeBSD x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.4.1
This is a follow up patch release for recent LibSass update which fixes the reported regressions.
Check out LibSass release notes (https://github.com/sass/libsass/releases/tag/3.3.1) for more information.
Version 3.4.0
Today we're proud to release v3.4.0 of Node Sass.
Acknowledgements
As always we want to thank our beloved contributors who breathe life into this piece of code. ❤️ @cvibhagool, @fh1ch, @JTKnox91, @kylecho, @pmq20 and everyone who opened issues. Without your contributions we wouldn't be where we are today.
Also a big thanks to the LibSass team and their contributors for their work!
We (@am11, @saper, @xzyfer) hope you all will enjoy this release 🚀
Changelog
LibSass 3.3.0
This release has the latest LibSass 3.3.0 release which brings with it major feature parity Ruby Sass*, massive speed improvements and MUCH MORE!
Check the changelog (https://github.com/sass/libsass/releases/tag/3.3.0)
Improvements
Added npm-config suppot the binary resolution configuration (@fh1ch, #1145)
Added a better error message if the binary download experience a network failure (@pmq20@saper, #1151)
Added symlink support to the CLI directory via the --follow (@dotzero, #1126)
Added automated Windows build for the native binary (@saper, #1135)
Fixes
Fix typo in README (@JTKnox91, #1157)
Fix typo in README (@cvibhagool, #1158)
Fix typo in README (@kylecho, #1159)
Version 3.4.0
This is hopefully the final beta release for the upcoming LibSass 3.3.0 release.
Acknowledgements
As always we want to thank our beloved contributors who breathe life into this piece of code. ❤️ @JTKnox91, @cvibhagool, @kylecho and everyone who opened issues. Without your contributions we wouldn't be where we are today.
Also a big thanks to the LibSass team and their contributors for their work!
We (@am11, @saper, @xzyfer) hope you all will enjoy this release 🚀
Changelog
LibSass 3.3.0-beta3
This beta release has the latest LibSass beta which fixes some regressions discovered by our beta testers.
Check the changelog (https://github.com/sass/libsass/releases/tag/3.3.0-beta2)
Fixes
Fix typo in README (@JTKnox91, #1157)
Fix typo in README (@cvibhagool, #1158)
Fix typo in README (@kylecho, #1159)
Version 3.4.0
The release you've all been waiting for! This is a beta release for the upcoming LibSass 3.3.0 release.
Acknowledgements
As always we want to thank our beloved contributors who breathe life into this piece of code. ❤️ @fh1ch, @pmq20 and everyone who opened issues. Without your contributions we wouldn't be where we are today.
Also a big thanks to the LibSass team and their contributors for their work!
We (@am11, @saper, @xzyfer) hope you all will enjoy this release 🚀
Changelog
LibSass 3.3.0-beta2
This beta release has the latest LibSass beta which brings with it major feature parity Ruby Sass*, massive speed improvements and MUCH MORE! (@saper, #1040)
Check the changelog (https://github.com/sass/libsass/releases/tag/3.3.0-beta1)
Improvements
Added npm-config suppot the binary resolution configuration (@fh1ch, #1145)
Added a better error message if the binary download experience a network failure (@pmq20@saper, #1151)
Added symlink support to the CLI directory via the --follow (@dotzero, #1126)
Added automated Windows build for the native binary (@saper, #1135)
Version 3.3.3
It's also contains a handful of fixes and build infrastructure improvements to prepare to recently release LibSass 3.3.0 betas (https://github.com/sass/libsass/releases/tag/3.3.0-beta1).
Node 4 compatibility
This release officially lands Node 4 support if you're building the native binding manually. For everyone else we had previously back ported precompiled Node 4 compatible native bindings to the v3.3.2 release.
Replace pangyp with node-gyp for Node 4 compatibility (@xzyfer, #1128)
Add Node.js 4.0 to our CI builds (@xzyfer, #1132, @gdi2290#1130)
Update native binding for Node.js 4 (@saper, #1054)
Improvements
Prepare for LibSass 3.3.0 (https://github.com/sass/libsass/releases/tag/3.3.0-beta1) betas (@saper, #1146)
Show compiler flags when building to improve debugging and error reporting (@saper, #1129)
Update to new Travis CI container infrastructure for faster builds (@xzyfer, #1117)
Standardise on using cross-spawn for spawning child processes (@xzyfer, #1015)
Update documentation for multi-file compilations to the clearer directory compilations (@xzyfer, #985)
Fixes
Fix race conditions in some tests (@saper, #1149#1150)
Fix poor error message when the LibSass binding is not found (@xzyfer, #1148)
Fix binding unnecessarily needing to be recompiled foriojs.exe and node.exe on Windows (@saper, #1147)
No longer use C++ exceptions in the binding code (@saper, #1133 fixing #1127 crash)
Fix custom functions returning sass.types.List(1) sometimes crashing (@saper, #1131)
Fix poor error message when calling render()/renderSync() without file or data (@saper, #924)
Version 3.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. (https://github.com/sass/node-sass/issues/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.
Version 3.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, https://github.com/sass/node-sass/issues/1107#issuecomment-134866739)
Version 3.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.
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.
Version 3.2.0
This release bumps Libsass to 3.2.5 which brings with it a bunch of fixes. Check the changelog (https://github.com/sass/libsass/releases/tag/3.2.5).
Features
Updated Libsass to 3.2.5 (@xzyfer, #992)
Version 3.1.2
Fixes
Fixed multi-file compilation sometimes writing to wrong file (#967, @kkopachev)
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.
Version 3.1.1
Fixes
Fixed ability to watch whole directory (#952, @kkopachev)
Version 3.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](https://github.com/sass/libsass/releases/tag/3.2.3) and [3.2.4 (https://github.com/sass/libsass/releases/tag/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.
Version 3.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 (https://github.com/sass/libsass/releases/tag/3.2.0).
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:
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.
Version 3.0.0
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 (https://github.com/sass/libsass/releases/tag/3.2.0-beta.6) 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.
Version 3.0.0
This release has been removed from npm due to release issue.
This has been superseded by v3.0.0-beta.7 (https://github.com/sass/node-sass/releases/tag/v3.0.0-beta.7)
Version 3.0.0
Installation:
npm install node-sass@beta
Changelog:
Implements libsass v3.2.0-beta.5 API.
Importer: Throws error on invalid return type.
Issue URL: #670.
PR URL: #833.
API: Provides support for array of importers.
Issue URL: #821.
PR URL: #832.
Feature: Provides sourceMapRoot option.
Issue URL: #776.
PR URL: #813.
CLI: Adds support for Custom Functions.
Issue URL: #784.
PR URL: #815.
CLI: Changes --watch flag Boolean by @wesleytodd.
Issue URL: #781.
PR URL: #782.
CLI: Sets --recursive flag default to true by @wesleytodd.
Issue URL: #601
PR URL: #782.
Build: Adding libsass.gyp in a separate dir.
Originally implemented by @saper, This was previously removed due to the bug in npm.
README: Formatting fixes by @tomfuertes.
Version 3.0.0
Installation:
From CLI:
npm install node-sass@beta
# or
npm install node-sass@3.0.0-beta.4
Or in package.json:
{
"dependencies": {
"node-sass": "beta"
}
}
Changelog:
Configurable linefeed by @matryo
Issue URL: #332.
PR URL: #644.
Provide options to configure linefeed by @am11
Issue URL: #682,
PR URL: #792.
Upstream PR URL: https://github.com/sass/libsass/pull/787.
Updates LibSass v3.2.0-beta.2 and corresponding Sass-Spec commit.
Reverts Build with unbundled LibSass. #763 by @saper, as it was causing issue with npm publish.
Note 1: This alpha version is not published to npm, but npm has the ability to figure out if you are requiring the GitHub release. For more information, see https://docs.npmjs.com/cli/install (keyword to search on page "commit-ish").
Note 2: You should have git in your PATH to be able to install GitHub tagged release via npm.
Changelog:
Build with unbundled LibSass. #763 by @saper.
Fixes bug #769, reported by @benpptung.
Version 3.0.0
npm install node-sass@3.0.0-alpha.0
Thanks to @lennym and @callumacrae for reporting npm publishing issue at #758.
CLI Usage: Fixed --watch bug reported by @IGRACH at #755.
Added .gitattributes, so publish issue from Windows don't happen again. Thanks @mgreter for suggesting the idea. https://github.com/sass/node-sass/pull/760
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi!
A new version was just released of
node-sass, so Doppinshas upgraded your project's dependency ranges.
Make sure that it doesn't break anything, and happy merging!
Upgraded node-sass from
2.1.1to3.8.0Changelog:
Version 3.8.0
Features
--error-bellCLI flag (@Peterhactch,#1578)cross-spawn-asyncwith cross-spawn (@danez,#1563)@xzyfer,#1538)jsdocfor public API functions (@nschonni,#1528)@xzyfer,#1523)@coderbyheart,#1506)Fixes
@nschonni,#1583)renderandrenderSyncbeing mutated (@xzyfer,#1168)Version 3.7.0
Node.js 6 support
You've asked, and asked, and asked... and here it is. It took a little longer than we'd hoped due a bug we discovered (
https://github.com/nodejs/node/issues/6500) in Node.js 6 which broken our Windows builds.Previous versions of Node Sass worked fine with Node.js 6 but produced scary looking warnings the console.
@saper,#1514)@xzyfer,#1484)@xzyfer,#1496)Update proxy support
Currently to detect user local settings, when downloading the precompiled binaries, we use a deprecated package. We've replaced this packaged with the offical npm environment variables. This drastically simplifies our install script.
Big thanks to
@delitescere! (#1333)Fixes
@xzyfer,#1500)@nschonni@xzyfer,#1487#1491)TODO URLin install error (@nschonni,#1488)@nschonni,#1486)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.6.0
LibSass
We've bumped LibSass to 3.3.6 Herbie (
https://github.com/sass/libsass/releases/tag/3.3.6)Fixes
#1464)Support Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.5.3
Fixes
@xzyfer)Support Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.5.2
Fixes
@xzyfer)Support Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.5.1
Deprecation
A previously undocumented
process.sasshas been deprecated (#1427). It will be removed in a future release. Access this API will produce a deprecation warning in the console.LibSass 3.3.5
This release includes the recent massive Delorean release as well as couple follow up bug fix release. We delayed this release until LibSass had fixed some issue that cropped in Delorean.
Check the changelogs for more information
https://github.com/sass/libsass/releases/tag/3.3.3)https://github.com/sass/libsass/releases/tag/3.3.4)https://github.com/sass/libsass/releases/tag/3.3.5)Improved installation errors
Say goodbye to this infamous error. The root cause is unavoidable but we can do a better job and helping you fix it without filing an issue. Thanks to
@xzyferyou'll now encounter something a bit more friendly!Custom functions
Thanks to
@eoneillcustom functions now have access to current render context viathis.The benefit of this is that custom functions can persist data (be stateful), for the lifespan of the
render. For example this is now possible:Features
@incompl,#1368)@qm3ster,#1363)--helptext has updated and improved (@glassdimly,#1177)npm pack(@gkatsev,#1183)@xzyfer,#1424)Fixes
@xzyfer,#1416)@nowellsand@beatakfor writing tests (#1381,#1420)@xzyfer,#1386)@saperfor tracking down the root causeMisc
@delitescere,#1413)npmconfdependency (@delitescere,#1413)bugsurl to package.json (@keithamus,#1367)Thanks!
As always the Node Sass would love to give a huge "thank you!" to all the contributors that made this release possible! We couldn't do it without you. ❤️ ❤️ ❤️
Support Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.5.0-beta.1
We're releasing this beta for the upcoming v3.5.0 release because of the LibSass bump. Please test this out and file any issue with Sass compilation.
LibSass
We've bumped LibSass to Delorean, check their changelog (
https://github.com/sass/libsass/releases/tag/3.3.3) for the juicy details.Windows XP support
In v3.4.2 LibSass and Node Sass starting compiling our prebuilt binaries with Visual Studio 2015 which caused issues for Windows XP users. After some incredible debugging and investigation by
@am11and@saperwe believe we have addressed the Window XP runtime errors.Features
@JohnAlbin,#1264)@saper,#1309)@xzyfer,#1319)requestwithgot(@zckrs,#1358)@saper,#1337)Fixes
@raithit,#1266)@ReadmeCritic,#1287)httpsrather thangitto check out LibSass in fallback compilation (@saper,#1301)@saper,#1307)sass.NULL(@saper,#1296)@nibblebot,#1212)@saper,#1323)@xzyfer,#1342)Misc
@ockham,#1269,@xzyfer#1321)@pra85,#1344)Version 3.4.2
Changelog
Features
https://github.com/sass/libsass/releases/tag/3.3.2) (@xzyfer,#1248)@xzyfer,#1248)Fixes
@xzyfer,#1260#1261)@ggamel,#1252)@jameslnewell,#1223)@chriseppstein,#1220)@jameslnewell,#1219)@esr360,@1218)Thanks
A big thanks to everyone who took the time report issues.
The LibSass team (
@hcatlin,@mgreter,@saper,@xzyfer) couldn't do this without your help.Support Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.4.1
This is a follow up patch release for recent LibSass update which fixes the reported regressions.
Check out LibSass release notes (
https://github.com/sass/libsass/releases/tag/3.3.1) for more information.Version 3.4.0
Today we're proud to release v3.4.0 of Node Sass.
Acknowledgements
As always we want to thank our beloved contributors who breathe life into this piece of code. ❤️
@cvibhagool,@fh1ch,@JTKnox91,@kylecho,@pmq20and everyone who opened issues. Without your contributions we wouldn't be where we are today.Also a big thanks to the LibSass team and their contributors for their work!
We (
@am11,@saper,@xzyfer) hope you all will enjoy this release 🚀Changelog
LibSass 3.3.0
This release has the latest LibSass 3.3.0 release which brings with it major feature parity Ruby Sass*, massive speed improvements and MUCH MORE!
Check the changelog (
https://github.com/sass/libsass/releases/tag/3.3.0)Improvements
@fh1ch,#1145)@pmq20@saper,#1151)--follow(@dotzero,#1126)@saper,#1135)Fixes
@JTKnox91,#1157)@cvibhagool,#1158)@kylecho,#1159)Version 3.4.0
This is hopefully the final beta release for the upcoming LibSass 3.3.0 release.
Acknowledgements
As always we want to thank our beloved contributors who breathe life into this piece of code. ❤️
@JTKnox91,@cvibhagool,@kylechoand everyone who opened issues. Without your contributions we wouldn't be where we are today.Also a big thanks to the LibSass team and their contributors for their work!
We (
@am11,@saper,@xzyfer) hope you all will enjoy this release 🚀Changelog
LibSass 3.3.0-beta3
This beta release has the latest LibSass beta which fixes some regressions discovered by our beta testers.
Check the changelog (
https://github.com/sass/libsass/releases/tag/3.3.0-beta2)Fixes
@JTKnox91,#1157)@cvibhagool,#1158)@kylecho,#1159)Version 3.4.0
The release you've all been waiting for! This is a beta release for the upcoming LibSass 3.3.0 release.
Acknowledgements
As always we want to thank our beloved contributors who breathe life into this piece of code. ❤️
@fh1ch,@pmq20and everyone who opened issues. Without your contributions we wouldn't be where we are today.Also a big thanks to the LibSass team and their contributors for their work!
We (
@am11,@saper,@xzyfer) hope you all will enjoy this release 🚀Changelog
LibSass 3.3.0-beta2
This beta release has the latest LibSass beta which brings with it major feature parity Ruby Sass*, massive speed improvements and MUCH MORE! (
@saper,#1040)Check the changelog (
https://github.com/sass/libsass/releases/tag/3.3.0-beta1)Improvements
@fh1ch,#1145)@pmq20@saper,#1151)--follow(@dotzero,#1126)@saper,#1135)Version 3.3.3
It's also contains a handful of fixes and build infrastructure improvements to prepare to recently release LibSass 3.3.0 betas (
https://github.com/sass/libsass/releases/tag/3.3.0-beta1).Node 4 compatibility
This release officially lands Node 4 support if you're building the native binding manually. For everyone else we had previously back ported precompiled Node 4 compatible native bindings to the
v3.3.2release.pangypwithnode-gypfor Node 4 compatibility (@xzyfer,#1128)@xzyfer,#1132,@gdi2290#1130)@saper,#1054)Improvements
https://github.com/sass/libsass/releases/tag/3.3.0-beta1) betas (@saper,#1146)@saper,#1129)@xzyfer,#1117)@xzyfer,#1015)multi-filecompilations to the clearerdirectorycompilations (@xzyfer,#985)Fixes
@saper,#1149#1150)@xzyfer,#1148)iojs.exeandnode.exeon Windows (@saper,#1147)@saper,#1133fixing#1127crash)sass.types.List(1)sometimes crashing (@saper,#1131)render()/renderSync()withoutfileordata(@saper,#924)Version 3.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 thev3.3.0andv.3.3.1npm packages whilst we figured out a solution. (https://github.com/sass/node-sass/issues/1107)Big thanks to everyone who reported the issue and helped
@saperand@xzyferdebug it.Big thanks to the
@kkoopaand@bnoordhuisfor a speedily releasingnan@2.0.8.Version 3.3.1
This release works arounds a segfault that occurs when Node Sass is used with
fsevents@0.3.8.Changelog
Bug fixes
fsevents@0.3.8(@xzyfer,https://github.com/sass/node-sass/issues/1107#issuecomment-134866739)Version 3.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
@saperto the team!Changelog
io.js v3 support
Thanks to a massive effort from
@saperand@kkoopawe update tonan@2which 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,#1053Let this be a reminder to always search before opening a new issue.
CI improvements
@am11@saperand@xzyferimplements various stability and speed improvements to our CI process. This will enable us to produced more frequent release.@saper,#1099)@am11,#1097)@xzyfer,#1096)@am11@saper,#966)@saper,#910)@saper,#1058)Minor features
@am11,#1033)Document updates
@Cydrobolt,#1094)outFileoption (@gpapin,#1084)indentedSyntaxoption (@dkebler,#1081)@saper,#1063)@saper,#1060)@am11,#1033)@amm,#1033)@JAFong,#1028)@lencioni,#1020)Bug fixes
.sassfiles (@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
@kkoopaand@saperfor all their hard work the io.js v3 compatibility.Version 3.2.0
This release bumps Libsass to 3.2.5 which brings with it a bunch of fixes. Check the changelog (
https://github.com/sass/libsass/releases/tag/3.2.5).Features
@xzyfer,#992)Version 3.1.2
Fixes
#967,@kkopachev)#903,@am11)Notes
Version 3.1.1
Fixes
#952,@kkopachev)Version 3.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
https://github.com/sass/libsass/releases/tag/3.2.3) and [3.2.4 (https://github.com/sass/libsass/releases/tag/3.2.4)Fixes
@saper@xzyfer,#945)package(@ajp427,#936)@xzyfer,#950)@akauppi,#928)Documentation
@antleblanc,#940)Thanks !
Big thank you to all our contributors, and to everyone who opened issues. Honourable mentions to
@ajp427,@akauppi,@am11,@antleblanc,@saperand@xzyfer.Version 3.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 (
https://github.com/sass/libsass/releases/tag/3.2.0).Secondly,
@xzyferhas been promoted to project lead. We all owe@am11a "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
@JakoboErrorobject instead ofStrings-@am11,@sindresorhusOld:
New:
Bufferoutput as opposed toString-@am11@am11@am11stdout-@am11,@xzyfer--watchflag is now boolean -@wesleytoddFeatures
@xzyfersourceMapRootoption -@am11@am11,@matryo--recursiveflag to true -@wesleytodd@xzyferthis.optionstoimporterandrendercallbacks -@Jakobo@am11,@johnrc,@saperSASS_BINARY_SITE-@am11,@nschonniUser-AgentHTTP header when fetching binaries -@saper@xzyferExperimental features
@am11@matryoDocumentation
@tomfuertes@am11,@mgreter@xzyferFixes
@am11,@xzyfer@saper,@am11@saper@saperKnown issues
#857)Thanks!
This release wouldn't be possible without the hard work of
@am11,@andyshora,@danielstjules,@Jakobo,@kevva,@matryo,@paulcpederson,@saper,@tomfuertes,@wesleytoddand@xzyfer.Version 3.0.0
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@am11and the previous projects for their incredible work making node-sass what it is. I can only hope to do their work justice.Installation
Changelog
Libsass
We've updated to latest libSass release.
Check out the 3.0.0-beta.6 changelog (
https://github.com/sass/libsass/releases/tag/3.2.0-beta.6) for more information.Features
@xzyfer,#872)--quietCLI flag (@paulcpederson,#841)@paulcpederson,#828)@am11,#697)@xzyfer,#874)Bug fixed
render(@saper,#713)@saper,#856)@andyshora,#842)outFile(@am11,#839)@am11,#837)Known issues
#857)#870)Thanks!
This release wouldn't be possible without the hard work of
@am11,@andyshora,@paulcpederson,@saper, and@xzyfer.Version 3.0.0
This release has been removed from npm due to release issue.
This has been superseded by v3.0.0-beta.7 (
https://github.com/sass/node-sass/releases/tag/v3.0.0-beta.7)Version 3.0.0
Installation:
Changelog:
#670.#833.#821.#832.sourceMapRootoption.#776.#813.#784.#815.--watchflag Boolean by@wesleytodd.#781.#782.--recursiveflag default to true by@wesleytodd.#601#782.@saper, This was previously removed due to the bug in npm.@tomfuertes.Version 3.0.0
Installation:
From CLI:
npm install node-sass@beta # or npm install node-sass@3.0.0-beta.4Or in
package.json:{ "dependencies": { "node-sass": "beta" } }Changelog:
@matryoIssue URL:
#332.PR URL:
#644.@am11Issue URL:
#682,PR URL:
#792.Upstream PR URL:
https://github.com/sass/libsass/pull/787.#763by@saper, as it was causing issue withnpm publish.Version 3.0.0
Installation:
From CLI:
Or in
package.json:{ "dependencies": { "node-sass": "sass/node-sass#v3.0.0-alpha.1" } }Note 1: This alpha version is not published to npm, but npm has the ability to figure out if you are requiring the GitHub release. For more information, see https://docs.npmjs.com/cli/install (keyword to search on page "commit-ish").
Note 2: You should have git in your PATH to be able to install GitHub tagged release via npm.
Changelog:
Build with unbundled LibSass.
#763by@saper.Fixes bug
#769, reported by@benpptung.Version 3.0.0
@lennymand@callumacraefor reporting npm publishing issue at#758.--watchbug reported by@IGRACHat#755..gitattributes, so publish issue from Windows don't happen again. Thanks@mgreterfor suggesting the idea.https://github.com/sass/node-sass/pull/760