Installation fail on Windows 10 #1276
Labels
Comments
|
Relevant lines are below. Doesn't really explain what went wrong. |
|
@NXTaar can you please provide the output of the following |
|
i did all things in troubleshooting section, wanted to edit top post)) C:\Projects\Work\FPB>mkdir \temp1 C:\Projects\Work\FPB>cd \temp1 C:\temp1>npm -v C:\temp1>node -v C:\temp1>node -p process.versions C:\temp1>node -p process.platform C:\temp1>node -p process.arch C:\temp1>npm cache clean C:\temp1>npm install -ddd node-sass > npm.log 2> npm.err C:\temp1> And the files |
|
This "node" не является внутренней или внешней командой, исполняемой программой или пакетным файлом means that npm could not find your node.exe on your PATH. Does @xzyfer unfortunately npm debug output is next to worthless for debugging lifecycle scripts.... |
|
This line waa questioning me to. Node was installed,ofcourse, PATH has it, and it works well. I thought that the node-sass during installation tries to run new node process with some special parameters needed for installation, but it fails |
|
|
|
Closing due to inactivity. Happy to reopen if there is additional information. |
|
Figured out what the problem was. It mostly related to the Windows environment as an OS and to the node-gyp package itself. The solution can be found here So basicly you can direct all your "Can't install node-sass on Windows %number%" to this solution, because it can solve 85% percent of the problem issues |
|
Thanks @NXTaar. If this issue crops up again it might be worth adding it to our troubleshooting docs. |
|
Thanks @NXTaar looks like it solves here for |
|
I also found helpful this comment. After installing Python 2.7 and Visual C++ Build Tools I deleted node_modules folder, opened CMD from Administrator and ran This link helped me to install Python and VS C++ build tools. |
Friendly-users
referenced
this issue
in Friendly-users/node-sass
Jul 9, 2024
----- It is inappropriate to include political and offensive content in public code repositories. Public code repositories should be neutral spaces for collaboration and community, free from personal or political views that could alienate or discriminate against others. Political content, especially that which targets or disparages minority groups, can be harmful and divisive. It can make people feel unwelcome and unsafe, and it can create a hostile work environment. Please refrain from adding such content to public code repositories.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, i can't proper install node-sass, for webpack integration.
here is log in cmd and my npm-debug.log https://gist.github.com/NXTaar/4c5fba3387529249f4bf
C:\Projects\Work\FPB\2.0>npm i node-sass --save-dev
npm WARN install Couldn't install optional dependency: Unsupported
npm WARN prefer global node-gyp@3.1.0 should be installed with -g
"node" не является внутренней или внешней
командой, исполняемой программой или пакетным файлом.
npm WARN EPACKAGEJSON paybox@1.0.0 No repository field.
npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\NXTaar\AppData\Roaming\npm\node_modules\np
m\bin\npm-cli.js" "i" "node-sass" "--save-dev"
npm ERR! node v5.0.0
npm ERR! npm v3.3.7
npm ERR! code ELIFECYCLE
npm ERR! node-sass@3.4.2 install:
node scripts/install.jsnpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@3.4.2 install script 'node scripts/install.js'.
npm ERR! 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/install.js
npm ERR! 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! C:\Projects\Work\FPB\2.0\npm-debug.log
C:\Projects\Work\FPB\2.0>
The text was updated successfully, but these errors were encountered: