Node sass ошибка при установке

Name already in use

node-sass / TROUBLESHOOTING.md

• Go to file T
• Go to line L
• Copy path
• Copy permalink

Copy raw contents

Copy raw contents

This document covers some common node-sass issues and how to resolve them. You should always follow these steps before opening a new issue.

If you see a 404 when trying to install node-sass, this indicates that you’re trying to install a version of node-sass that doesn’t support your version of NodeJS, or uses an alternate V8 environment (Meteor, Electron, etc. ) that isn’t supported by node-sass.

If you encounter this, please check what version of NodeJs you’re running ( node -v ) and check for a supported version of node-sass for your NodeJs by checking our release page.

If you work in behind a corporate proxy try setting the proxy variables. The following is a guide for setting this up.

Running with sudo or as root

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.

If 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 before 5 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:

The easiest way to get around this is just to cleanup the npm files and reinstall.

Helping us, help you

Find what version of Node you’re running

To determine which version of Node.js or io.js you are currently using run the following command in a terminal.

The resulting value the version you are running.

Debugging installation issues

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.

Check your COMSPEC environment variable.

Please make sure the variable points to C:WINDOWSSystem32cmd.exe

Gather some basic diagnostic information.

Clean npm cache

Install the latest node-sass

Note which version was installed by running

If node-sass couldn’t 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 information.

If the node-sass installation process produced an error, open the vendor folder.

Then, using the version number we gather at the beginning, go to https://github.com/sass/node-sass/releases/tag/v .

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 information.

If this still produces an error please open an issue with the output from these steps.

Firstly create a clean work space.

Gather some basic diagnostic information.

Install the latest node-sass

Note which version was installed by running

If node-sass install successfully lets gather some basic installation information.

If the node-sass installation process produced an error, open the vendor folder.

Then, using the version number we gather at the beginning, go to https://github.com/sass/node-sass/releases/tag/v .

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 information.

If this still produces an error please open an issue with the output from these steps.

Using node-sass with Visual Studio 2015 Task Runner

Источник

Can not install node-sass — ERR! Failed at the node-sass@4.5.3 postinstall script ‘node scripts/build.js’. #1980

I have an error when i run npm install node-sass , i have already the last versions of node and npm (LTS) and previously already installed npm install -g windows-build-tools

Please, i need your help i can not figure out what is the issue?, and how to solved.

This is my platform:

• NPM version ( npm -v ): 3.10.10
• Node version ( node -v ): 6.10.3
• Node Process ( node -p process.versions ):

• Node Platform ( node -p process.platform ): win32
• Node architecture ( node -p process.arch ): x64
• node-sass version ( node -p «require(‘node-sass’).info» ):
• npm node-sass versions ( npm ls node-sass ):

Error message from npm install node-sass

postinstall: unsafe-perm in lifecycle true npm verb lifecycle node-sass@4.5.3

postinstall: PATH: C:Program Filesnodejsnode_modulesnpmbinnode-gyp-bin;C:Users carlosmAppDataRoamingnpmnode_modulesnode-sassnode_modules.bin;C:UserscarlosmAppDataRoamingnpmnode_modules .bin;%SystemRoot%system32WindowsPowerShellv1.0;C:Python27;C:Python27Scripts;C:appsoracleproduct11.2.0client _1bin;C:ProgramDataOracleJavajavapath;C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem;C:WindowsSystem32W indowsPowerShellv1.0;C:Program FilesTortoiseSVNbin;C:Program Filesnodejs;C:Program Files (x86)Windows Kits8.1 Windows Performance Toolkit;$PATH;D:JAVAapache-tomcat-8.0.9/bin;C:Program Files (x86)VSCode-win32-1.11.2;C:Pytho n27;C:UserscarlosmAppDataRoamingnpm npm verb lifecycle node-sass@4.5.3

postinstall: CWD: C:UserscarlosmAppDataRoamingnpmnode_modulesnode-sass npm info lifecycle node-sass@4.5.3

I follow the template, please do not close the issue, i have already three day without solution to this issue

The text was updated successfully, but these errors were encountered:

postinstall: unsafe-perm in lifecycle truenpm verb lifecycle ***@***.***

postinstall: PATH: C:Program Filesnodejsnode_modulesnpmbinnode-gyp-bin;C:UserscarlosmAppDataRoamingnpmnode_modulesnode-sassnode_modules.bin;C:UserscarlosmAppDataRoamingnpmnode_modules.bin;%SystemRoot%system32WindowsPowerShellv1.0;C:Python27;C:Python27Scripts;C:appsoracleproduct11.2.0client_1bin;C:ProgramDataOracleJavajavapath;C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem;C:WindowsSystem32WindowsPowerShellv1.0;C:Program FilesTortoiseSVNbin;C:Program Filesnodejs;C:Program Files (x86)Windows Kits8.1Windows Performance Toolkit;$PATH;D:JAVAapache-tomcat-8.0.9/bin;C:Program Files (x86)VSCode-win32-1.11.2;C:Python27;C:UserscarlosmAppDataRoamingnpmnpm verb lifecycle ***@***.***

postinstall: CWD: C:UserscarlosmAppDataRoamingnpmnode_modulesnode-sassnpm info lifecycle ***@***.***

Источник

Node sass ошибка при установке

Reading time В· 2 min

Cannot find module ‘node-sass’ error #

To solve the error «Cannot find module ‘node-sass’», make sure to install the node-sass package by opening your terminal in your project’s root directory and running the following command: npm i -D node-sass and restart your IDE and development server.

Open your terminal in your project’s root directory (where your package.json file is located) and run the following command:

This will add the node-sass package to the development dependencies of your project.

If you still get the error, try to install the package with the —unsafe-perm flag.

If the command above fails with a permissions error, try prefixing it with sudo .

The —unsafe-perm flag forces npm to download the node-sass binary to your project.

Delete your node_modules and reinstall your dependencies #

If the error is not resolved, try to delete your node_modules and package-lock.json (not package.json ) files, re-run npm install and restart your IDE.

Verify your Node.js version matches your node-sass version #

If you still get the error, open the npm page of node-sass and look at the Node version support policy.

7 ответов

$ npm install node-sass --save-dev-
                                 ^^^

$ npm install node-sass --save-dev

npm uninstall --save-dev gulp-sass

$ npm install --save-dev [email protected]