Angular-cli: Error to new install angular/[email protected] with npm

Created on 30 May 2019  ·  13Comments  ·  Source: angular/angular-cli

🐞 Bug report

Command (mark with an x or write it if not found the right command)


[sudo] npm i -g @angular/cli

Is this a regression?

I can install the latest version (7.3.9)

Description

When try install the last version of angular-cli npm package the command output a error and the installation process exited with status 130.
I tried install with and without sudo privileges.

🔬 Minimal Reproduction

Run this command: npm i -g @angular/cli

🔥 Exception or Error

The npm output when run the install command:


[        ..........] \ extract:genfun: sill extract [email protected]
/usr/local/bin/ng -> /usr/local/lib/node_modules/@angular/cli/bin/ng

> @angular/[email protected] postinstall /usr/local/lib/node_modules/@angular/cli
> node ./bin/postinstall/script.js

? Would you like to share anonymous usage data with the Angular Team at Google under
Google’s Privacy Policy at https://policies.google.com/privacy? For more details and
npm ERR! code ELIFECYCLE
npm ERR! errno 130
npm ERR! @angular/[email protected] postinstall: `node ./bin/postinstall/script.js`
npm ERR! Exit status 130
npm ERR! 
npm ERR! Failed at the @angular/[email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/aran/.npm/_logs/2019-05-30T12_29_27_291Z-debug.log

And the log that npm create with the error (I've create a github gist because the file is too long):
Gist Log

🌍 Your Environment

NPM version: 6.4.1
OS: Ubuntu 18.04

Anything else relevant?

...?

angulacli low regression bufix
Source
picture amoncusir
👍4

Most helpful comment

When installed node and npm with snap I had to run the following command in order to install @angular/cli globally:

sudo npm install -g @angular/cli --scripts-prepend-node-path

picture renantarouco on 5 Jun 2019
👍4 🚀1 🎉1

All 13 comments

In case it helps I tried to update Nodejs (v12.3.1) and NPM (v6.9.0) and the problem not solve.

amoncusir picture amoncusir on 30 May 2019

Hey! I finded a fast solution for solve this problem. I one of my attempts to know what happens, I see that if create a new user in the same os environment, the problem nothing happens.

My solution is remove all user data related with npm and angular cli, like .angular-config.json user file, .npm folder, .cache folder and others (I don't remember all files that I removed :cry:)

That is possible it angular save any state or any others files in user folder? Or that it npm save any state or other think?

Thank's!

amoncusir picture amoncusir on 31 May 2019
👎9 😕3 👍1

I am having the same exact issue. Tried deleting .angular-config.json, .npm and .cache folders, but it's still not working.

npm -v
6.9.0

node -v
v10.16.0

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:    18.04
Codename:   bionic

sudo npm -g install @angular/[email protected]
/usr/bin/ng -> /usr/lib/node_modules/@angular/cli/bin/ng

> @angular/[email protected] postinstall /usr/lib/node_modules/@angular/cli
> node ./bin/postinstall/script.js

? Would you like to share anonymous usage data with the Angular Team at Google under
Google’s Privacy Policy at https://policies.google.com/privacy? For more details and
how to change this setting, see http://angular.io/analytics. No
(node:7863) UnhandledPromiseRejectionWarning: Error: EACCES: permission denied, open '/home/abcde/.angular-config.json'
    at Object.openSync (fs.js:443:3)
    at Object.writeFileSync (fs.js:1194:35)
    at createGlobalSettings (/usr/lib/node_modules/@angular/cli/utilities/config.js:65:10)
    at Object.getWorkspaceRaw (/usr/lib/node_modules/@angular/cli/utilities/config.js:73:26)
    at setAnalyticsConfig (/usr/lib/node_modules/@angular/cli/models/analytics.js:288:43)
    at Object.promptGlobalAnalytics (/usr/lib/node_modules/@angular/cli/models/analytics.js:326:9)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:7863) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7863) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
+ @angular/[email protected]
updated 1 package in 7.565s

@amoncusir could you check your command history and see what else you deleted? Thanks!

grandtiger picture grandtiger on 5 Jun 2019
👍1

Having the exact same issue

[~]# which npm

/bin/npm

[~]# npm -v

6.9.0

[~]# which node

/bin/node

[~]# node -v

v10.16.0

[~]# lsb_release -a

LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.6.1810 (Core)
Release: 7.6.1810
Codename: Core

[~]# npm list -g --depth=1

/usr/lib
├─┬ @angular/[email protected]
│ ├── @angular-devkit/[email protected]
│ ├── @angular-devkit/[email protected]
│ ├── @angular-devkit/[email protected]
│ ├── @schematics/[email protected]
│ ├── @schematics/[email protected]
│ ├── @yarnpkg/[email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
└─┬ [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── lodash.[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

[~]npm install -g @angular/cli

/usr/bin/ng -> /usr/lib/node_modules/@angular/cli/bin/ng
> @angular/[email protected] postinstall /usr/lib/node_modules/@angular/cli
> node ./bin/postinstall/script.js

? Would you like to share anonymous usage data with the Angular Team at Google under
Google’s Privacy Policy at https://policies.google.com/privacy? For more details and
how to change this setting, see http://angular.io/analytics. No
(node:7812) UnhandledPromiseRejectionWarning: Error: EACCES: permission denied, open '/root/.angular-config.json'
at Object.openSync (fs.js:443:3)
at Object.writeFileSync (fs.js:1194:35)
at createGlobalSettings (/usr/lib/node_modules/@angular/cli/utilities/config.js:65:10)
at Object.getWorkspaceRaw (/usr/lib/node_modules/@angular/cli/utilities/config.js:73:26)
at setAnalyticsConfig (/usr/lib/node_modules/@angular/cli/models/analytics.js:288:43)
at Object.promptGlobalAnalytics (/usr/lib/node_modules/@angular/cli/models/analytics.js:326:9)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:7812) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7812) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
+ @angular/[email protected]
added 227 packages from 175 contributors in 36.211s

jimploof picture jimploof on 5 Jun 2019

When installed node and npm with snap I had to run the following command in order to install @angular/cli globally:

sudo npm install -g @angular/cli --scripts-prepend-node-path

renantarouco picture renantarouco on 5 Jun 2019
👍4 🚀1 🎉1

same here , all build using ng-cli were broken,
(the build do a local temporary install of node & ng-cli )
added the following in the build scripts and the issue was solved

npm config set script-prepend-node-path true

ylorph picture ylorph on 6 Jun 2019
👍2

Nothing mentioned worked for me, additionally, everything I have found says not to install as root, or using sudo.

I followed some official documentation from npm manual and it worked for me.
https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally

jimploof picture jimploof on 6 Jun 2019
👍3

I just ran into the same issue. Using yarn appears to work just fine until they fix this:

yarn add global @angular/cli

qdouble picture qdouble on 8 Jun 2019

Run npm install -g @angular/cli without sudo. It worked for me.

ionutgrecu picture ionutgrecu on 12 Jun 2019

Not sure if this helps, none of above mentioned worked for me.
Still getting

? Would you like to share anonymous usage data with the Angular Team at Google under
Google’s Privacy Policy at https://policies.google.com/privacy? For more details and
npm ERR! code ELIFECYCLE
npm ERR! errno 130
npm ERR! @angular/[email protected] postinstall: `node ./bin/postinstall/script.js`
npm ERR! Exit status 130

And if I tried with
yarn add global @angular/cli

Following error occurs

2019/06/14 13:54:54 [~]$ yarn add global @angular/cli
yarn add v1.16.0
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
error /home/ubuntu/node_modules/@angular/cli: Command failed.
Exit code: 1
Command: node ./bin/postinstall/script.js
Arguments:
Directory: /home/ubuntu/node_modules/@angular/cli
Output:
/home/ubuntu/node_modules/rxjs/internal/util/hostReportError.js:4
    setTimeout(function () { throw err; });
                             ^

UnexpectedEndOfInputException [Error]: Unexpected end of file.
    at _readValue (/home/ubuntu/node_modules/@angular-devkit/core/src/json/parser.js:624:19)
    at parseJsonAst (/home/ubuntu/node_modules/@angular-devkit/core/src/json/parser.js:721:17)
    at Object.parseJson (/home/ubuntu/node_modules/@angular-devkit/core/src/json/parser.js:753:16)
    at MapSubscriber.project (/home/ubuntu/node_modules/@angular-devkit/core/src/experimental/workspace/workspace.js:259:175)
    at MapSubscriber._next (/home/ubuntu/node_modules/rxjs/internal/operators/map.js:49:35)
    at MapSubscriber.Subscriber.next (/home/ubuntu/node_modules/rxjs/internal/Subscriber.js:66:18)
    at MapSubscriber._next (/home/ubuntu/node_modules/rxjs/internal/operators/map.js:55:26)
    at MapSubscriber.Subscriber.next (/home/ubuntu/node_modules/rxjs/internal/Subscriber.js:66:18)
    at Observable._subscribe (/home/ubuntu/node_modules/@angular-devkit/core/node/host.js:191:21)
    at Observable._trySubscribe (/home/ubuntu/node_modules/rxjs/internal/Observable.js:44:25)
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
87CSY picture 87CSY on 14 Jun 2019

My problem was the following:

npm install -g @angular/cli
npm ERR! path /Users/acme/.npm/_cacache/index-v5/48/99
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall mkdir
npm ERR! Error: EACCES: permission denied, mkdir '/Users/acme/.npm/_cacache/index-v5/48/99'

As it turned out, user 'acme' was given no permissions to folder '48'. Assigning 'everyone' 'Read & Write' permissions to folder 'index-v5' fixed the problem for now.

lvhellgren picture lvhellgren on 1 Aug 2019

I got the same problem but I solved mine by running CMD as adminsitrator.

talent93 picture talent93 on 6 Aug 2019

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._

angular-automatic-lock-bot[bot] picture angular-automatic-lock-bot[bot] on 9 Sep 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

rwillmer picture rwillmer  ·  3Comments
hareeshav picture hareeshav  ·  3Comments
jbeckton picture jbeckton  ·  3Comments
sysmat picture sysmat  ·  3Comments
naveedahmed1 picture naveedahmed1  ·  3Comments