Node-sass: npm install stops at "node scripts/install.js" without any error

[realbugger]

So I got this really weird issue. I was running npm install in Ubuntu 14.04LTS, the installation just stops and exits at node scripts/install.js without throwing any error message. However, the installation went through without any problem on my windows 10 machine. Both machine has the same node and npm version (node: v5.9.0, npm: v3.7.3). I even tried different version of node and npm (node v5.11 and npm v3.8) but got the same issue. Has anyone encountered similar issue?

Here is the screen output, which doesn't really say much. The WARNs doesn't seem to be an issue. Even after clear them by updating the packages in my package.json file, the issue persists.

ubuntu@ubuntu:~/proj$ npm install --unsafe-perm
npm WARN deprecated [email protected]: Replaced by bootstrap-loader. Please upgrade.
npm WARN deprecated [email protected]: Please use postcss-loader instead of autoprefixer-loader
npm WARN deprecated [email protected]: Deprecated.
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN prefer global [email protected] should be installed with -g

> [email protected] install /home/ubuntu/adxfront/node_modules/node-sass
> node scripts/install.js

ubuntu@ubuntu:~/proj$

[xzyfer]

I have never seen this. With any luck an npm-debug.log file would have been
created with more information.
On 27 May 2016 8:30 AM, "Peng Han" [email protected] wrote:

So I got this really weird issue. I was running npm install in Ubuntu
14.04LTS, the installation just stops and exits at node scripts/install.js
without throwing any error message. However, the installation went through
without any problem on my windows 10 machine. Both machine has the same
node and npm version (node: v5.9.0, npm: v3.7.3). I even tried different
version of node and npm (node v5.11 and npm v3.8) but got the same issue.
Has anyone encountered similar issue?

Here is the screen output, which doesn't really say much. The WARNs
doesn't seem to be an issue. Even after clear them by updating the packages
in my package.json file, the issue persists.

ubuntu@ubuntu:~/proj$ npm install --unsafe-perm
npm WARN deprecated [email protected]: Replaced by bootstrap-loader. Please upgrade.
npm WARN deprecated [email protected]: Please use postcss-loader instead of autoprefixer-loader
npm WARN deprecated [email protected]: Deprecated.
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN prefer global [email protected] should be installed with -g

[email protected] install /home/ubuntu/adxfront/node_modules/node-sass
node scripts/install.js

ubuntu@ubuntu:~/proj$

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1568, or mute the thread
https://github.com/notifications/unsubscribe/AAjZWNd-A2-frs-au_47O5Gx9oumDN3mks5qFh8DgaJpZM4IoA5O
.

[realbugger]

It turned out to be a memory issue. The machine that had this issue was a AWS T2.micro instance with 1G memory. Normally 1G should be more than sufficient but in my case I have a long list of packages in my package.json. The installed node_modules folder is more than 160MB.

Later I tried the same installation on my Ubuntu virtual machine, which has exactly the same configuration as the AWS instance except it has 4G memory. And the installation went through with no problem. So I went back to the AWS instance and added 3G of swap space. Now everything is back to normal. This could be an easy problem but not throwing any error makes troubleshooting so much harder.

[bakura10]

Hi,

I'm having the exact same issue (it used to work correctly in the past so I don't due if it's due to a new version of a dependency):

> [email protected] install /Users/michael/Sites/skeleton/node_modules/node-sass
> node scripts/install.js

I've let it go for two full hours, and still stuck here. No errors, no npm-debug file generated... nothing :/. I was on Node 5.6, I've tried to upgrade to Node 6, same issue. Is this issue known?

[zhangmx]

@bakura10

I use vagrant with homestead to make a laravel project, and stuck at node-sass installing.

node version is 5, npm 3.3.6.

After I use npm install with 'sudo',this problem had solved.

Maybe you can try sudo npm install

[xzyfer]

Please don't even use sudo with npm install. It'll will cause all kinds of
permission errors. If you're having permission problems try using the
--unsafe-perm flag running npm install.
On 12 Jun 2016 9:44 AM, "腹肌抽筋了" [email protected] wrote:

@bakura10 https://github.com/bakura10

I use vagrant with homestead to make a laravel project, and stuck at
node-sass installing.

node version is 5, npm 3.3.6.

After I use npm install with 'sudo',this problem had solved.

Maybe you can try sudo npm install

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1568#issuecomment-225400697,
or mute the thread
https://github.com/notifications/unsubscribe/AAjZWKCM38e1dlarYzRHXAi3iyOXfJtAks5qK0hngaJpZM4IoA5O
.