npm install -g angular-cli: Killed #2630

Activity

1. BenDevelopment commented on Oct 10, 2016

   

   BenDevelopment

   on Oct 10, 2016

   Author

   More actions

   Ok according to this issue #1192, it's because angular cli need at least 1GB Ram. I only have 512.
2. filipesilva commented on Oct 10, 2016

   

   filipesilva

   on Oct 10, 2016

   Contributor

   More actions

   We do have a very big dependency tree now, yes (#1263). That causes some machines to have problems with npm install. There isn't much I can do to help now :/
3. filipesilva

   closed this as completedon Oct 10, 2016
4. khaidinh commented on Apr 28, 2017

   

   khaidinh

   on Apr 28, 2017

   More actions

   Ran into this issue as well and came across this solution. I followed the DigitalOcean guide for adding swap instead though.

   🎉React with 🎉1Reacted by Bagaskara Wisnu Gunawan
5. DMW007 commented on Oct 22, 2017

   

   DMW007

   on Oct 22, 2017

   More actions

   I ran into this issue on my Raspberry Pi 3 with 1 GB RAM. Don't know how Angular-CLI install the npm packages, but for me the following worked: Create your Angular app without installing all the packages using --skip-install switch like ng new client --skip-install. Then go to the directory (here with cd client) and run npm install.

   This is going to take a while on my RPI3 and result in memory peaks of about 800 MB and also the 100MB swap are full. So there shouldn't be to much running apps on it. But using this methods, it seems that all dependencies were installed:

   root@1ce293b0533c:/app/client# npm install
   npm WARN prefer global node-gyp@3.6.2 should be installed with -g
   
   > node-sass@4.5.3 install /app/client/node_modules/node-sass
   > node scripts/install.js
   

   Now it serves successfully using ng serve (note that --public-host fixes this issue where we get a Invalid host header error in the browser)

   root@1ce293b0533c:/app/client# ng serve --host=0.0.0.0 --port=3000 --public-host=http://pi3
   ** NG Live Development Server is listening on 0.0.0.0:3000, open your browser on http://localhost:3000/ **
    94% asset optimizationwebpack: wait until bundle finished: /                                                                                                  Date: 2017-10-22T09:35:45.942Z
   Hash: f258b747399558a50cdf
   Time: 69959ms
   chunk {inline} inline.bundle.js, inline.bundle.js.map (inline) 5.83 kB [entry] [rendered]
   chunk {main} main.bundle.js, main.bundle.js.map (main) 8.62 kB {vendor} [initial] [rendered]
   chunk {polyfills} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 199 kB {inline} [initial] [rendered]
   chunk {styles} styles.bundle.js, styles.bundle.js.map (styles) 11.3 kB {inline} [initial] [rendered]
   chunk {vendor} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.32 MB [initial] [rendered]
   
   webpack: Compiled successfully.
   
6. angular-automatic-lock-bot commented on Sep 7, 2019

   

   angular-automatic-lock-botbot

   on Sep 7, 2019

   More actions

   This issue has been automatically locked due to inactivity.
   Please file a new issue if you are encountering a similar or related problem.

   Read more about our automatic conversation locking policy.

   _{This action has been performed automatically by a bot.}
7. angular-automatic-lock-bot

   locked and limited conversation to collaborators on Sep 7, 2019