This document covers some common node-sass issues and how to resolve them. You should always follow these steps before opening a new issue.
- Installation problems
- Glossary
- Using node-sass with Visual Studio 2015 Task Runner.
- Installing node-sass 4.x with Node < 4
This issue primarily affected early node-sass@3.0.0 alpha and beta releases, although it did occassionally happen in node-sass@2.x.
The only fix for this issue is to update to node-sass >= 3.0.0.
If this didn't solve your problem please open an issue with the output from our debugging script.
This can happen if you are install node-sass as root, or globally with sudo. This is a security feature of npm. You should always avoid running npm as sudo because install scripts can be unintentionally malicious.
Please check npm documentation on fixing permissions.
If you must however, you can work around this error by using the --unsafe-perm flag with npm install i.e.
$ sudo npm install --unsafe-perm -g node-sassIf this didn't solve your problem please open an issue with the output from our debugging script.
Some users upgrading from previous versions of npm have found conflicts with old lock file formats. This may be show up as a URL instead of the actual version number when downloading the binary. EX:
Downloading binary from https://github.com/sass/node-sass/releases/download/vhttps://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz/win32-x64-57_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/vhttps://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz/win32-x64-57_binding.node":
HTTP error 404 Not FoundThe easiest way to get around this is just to cleanup the npm files and reinstall.
rm -rf node_modules
rm package-lock.json
npm cache clean
npm installThere are two primary node runtimes, Node.js and io.js, both of which are supported by node-sass. To determine which you are currently using you first need to determine which node runtime you are running.
node -v
If the version reported begins with a 0, you are running Node.js, otherwise you are running io.js.
To determine which version of Node.js or io.js you are currenty using run the following command in a terminal.
node -v
The resulting value the version you are running.
Node sass runs some install scripts to make it as easy to use as possible, but some times there can be issues. Before opening a new issue please follow the instructions for Windows or Linux/OSX and provide their output in you GitHub issue.
Remember to always search before opening a new issue.
Firstly create a clean work space.
mkdir \temp1
cd \temp1Check your COMSPEC environment variable.
node -p process.env.comspecPlease make sure the variable points to C:\WINDOWS\System32\cmd.exe
Gather some basic diagnostic information.
npm -v
node -v
node -p process.versions
node -p process.platform
node -p process.archClean npm cache
npm cache cleanInstall the latest node-sass
npm install -ddd node-sass > npm.log 2> npm.errNote which version was installed by running
npm ls node-sassy@1.0.0 /tmp
└── node-sass@3.8.0If node-sass could not be installed successfully, please publish your npm.log
and npm.err files for analysis.
You can download reference known-good logfiles to compare your log against.
If node-sass install successfully lets gather some basic installation infomation.
node -p "require('node-sass').info"node-sass 3.8.0 (Wrapper) [JavaScript]
libsass 3.3.6 (Sass Compiler) [C/C++]If the node-sass installation process produced an error, open the vendor folder.
cd node_modules\node-sass\vendorThen, using the version number we gather at the beginning, go to https://github.com/sass/node-sass/releases/tag/v<your-version>.
There you should see a folder with same name as the one in the vendor folder. Download the binding.node file from that folder and replace your own with it.
Test if that worked by gathering some basic installation infomation.
node -p "require('node-sass').info"node-sass 3.8.0 (Wrapper) [JavaScript]
libsass 3.3.6 (Sass Compiler) [C/C++]If this still produces an error please open an issue with the output from these steps.
Firstly create a clean work space.
mkdir ~/temp1
cd ~/temp1Gather some basic diagnostic information.
npm -v
node -v
node -p process.versions
node -p process.platform
node -p process.archInstall the latest node-sass
npm install node-sassNote which version was installed by running
npm ls node-sassy@1.0.0 /tmp
└── node-sass@3.8.0If node-sass install successfully lets gather some basic installation infomation.
node -p "require('node-sass').info"node-sass 3.8.0 (Wrapper) [JavaScript]
libsass 3.3.6 (Sass Compiler) [C/C++]If the node-sass installation process produced an error, open the vendor folder.
cd node_modules/node-sass/vendorThen, using the version number we gather at the beginning, go to https://github.com/sass/node-sass/releases/tag/v<your-version>.
There you should see a folder with same name as the one in the vendor folder. Download the binding.node file from that folder and replace your own with it.
Test if that worked by gathering some basic installation infomation.
node -p "require('node-sass').info"node-sass 3.8.0 (Wrapper) [JavaScript]
libsass 3.3.6 (Sass Compiler) [C/C++]If this still produces an error please open an issue with the output from these steps.
If you are using node-sass with VS2015 Task Runner Explorer, you need to make sure that the version of node.js (or io.js) is same as the one you installed node-sass with. This is because for each node.js runtime modules version (node -p process.versions.modules), we have a separate build of native binary. See #532.
Alternatively, if you prefer using system-installed node.js (supposedly higher version than one bundles with VS2015), you may want to point Visual Studio 2015 to use it for task runner jobs by following the guidelines available at: http://blogs.msdn.com/b/webdev/archive/2015/03/19/customize-external-web-tools-in-visual-studio-2015.aspx.
See the discussion in this comment for a workaround. As of node-sass@v5 only Node 6 and above will be offically supported.