New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue Installing Node-Sass - ELIFECYCLE #1932
Comments
Can you provide the full log in a Gist? |
|
@noraj1337 3.13.1 is old and doesn't support Node 8. It also used a submodule for the libsass files, which appears not to have been initialized if it can't find the header. Closing since the original poster never responded |
I know it's old but https://github.com/knksmith57/hexo-renderer-sass was using it. And yes I was using Node 8. |
There's nothing we can do. You can either ask them to update their
node-sass dependency to 4.5+ or down grade your node.
…On 27 Jun. 2017 7:15 am, "Alexandre ZANNI" ***@***.***> wrote:
I know it's old but https://github.com/knksmith57/hexo-renderer-sass was
using it. And yes I was using Node 8.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1932 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWCU0V5zLOMdInJkuKpVoEYoxcs2cks5sIB9cgaJpZM4MpoTo>
.
|
I had similar problem. I switched to new machine and i expected that i just retrieve whole code from git, then just npm install and npm run build, but it stuck on getting node-sass 3.13.1. It still worked on my second computer, because this module was downloaded long time ago. The question is if this release: https://github.com/sass/node-sass/releases/download/v3.13.1/win32-ia32-57_binding.node existed half year ago and then you removed it. If yes, then people cannot trust this source anymore - suddenly your application does not build because brand new build machine didnt have your modules cached. |
@mstrzoda there was never a binary provide for Node 8 for 3.13.1 |
@nschonni a ok, so i had node 8, and npm tried to download node-sass 3.13.1 for node 8, which never existed, and on my old computer and on server we had older node, that's why it worked there. Complicated like Lost plot, but makes sense. Thank you! |
@nschonni How to force npm to use node-sass 4.6.1 for node 8 and npm 5.5.1 instead of 3.13.1 |
Trying to install a package that uses node-sass. No luck!
Every time I try to run 'npm install' or 'sudo npm install' in the app folder (where package.json is located) it breaks whenever it tries to install node-sass:
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@3.13.1 install:
node scripts/install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@3.13.1 install script 'node scripts/install.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/install.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! A complete log of this run can be found in:
npm ERR! /home/vagrant/.npm/_logs/2017-03-26T09_46_56_175Z-debug.log
Tried to install node-sass globally using: 'sudo npm install node-sass' and got the same error ELIFECYCLE.
BUT, when i tried 'sudo PATH="$PATH:/usr/bin" npm install node-sass, IT WORKED.
I could install node-sass globally.
Then I thought it was a PATH issue and tried 'sudo PATH="$PATH:/usr/bin" npm install node-sass' (or just npm install, to try to install the whole package).
No luck!
Always receiving this "ELIFECYCLE" error.
I´m new to Linux, used to develop in Windows + Xampp.
NPM version (
npm -v
): 4.4.4Node version (
node -v
): 6.10.1Node Process (
node -p process.versions
): versions{ http_parser: '2.7.0',
node: '6.10.1',
v8: '5.1.281.95',
uv: '1.9.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
icu: '56.1',
modules: '48',
openssl: '1.0.2k' }
Node Platform (
node -p process.platform
): linuxNode architecture (
node -p process.arch
): x64node-sass version (
node -p "require('node-sass').info"
):node-sass 4.5.1 (Wrapper) [JavaScript]
libsass 3.5.0.beta.2 (Sass Compiler) [C/C++]
npm node-sass versions (
npm ls node-sass
): -- (empty)The text was updated successfully, but these errors were encountered: