npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! Linux 4.10.0-35-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v6.11.3
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! node-sass@4.5.3 postinstall: `node scripts/build.js`
npm ERR! Exit status 135
npm ERR!
npm ERR! Failed at the node-sass@4.5.3 postinstall script 'node scripts/build.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/phani/Documents/phani/Work/my projects/Running/billing/npm-debug.log
Hi, can you just confirm the command(s) you are running to get this output? Are you trying to install node-sass independently? Is it part of a different package?
I don’t even know what is node-sass .
I am not installing it so may be it is in the package
well, that’s the whole point of a package manager, to install packages required for the package you desire without you having to install everything by yourself.
So now how to resolve this issue
Original question: what is the command you are running to generate that output?
start by doing what npm suggests:
mine is 8.6.0.
that is the latest one
and npm ?
looks like somewhat outdated versions to me …
I think i updated later on so ieill check agian.
Thanks for the help
You shouldn’t be having a problem with 6 considering it is the most recent stable version. Version 8 is bleeding edge… I wouldn’t recommend using that except for experimental purposes. I have found these issues normally boil themselves down to permission issues. Did you install node as sudo by chance and running the install of node-sass as another user. That could be a cause.
I used the command it both with and without sudo
So back to the earlier question then, what command are you using to generate that output?
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.