Skip to content

Ng new app_name fails to install @angular/[email protected] #1104

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

Closed
alexandrearc opened this issue Jun 16, 2016 · 3 comments
Closed

Ng new app_name fails to install @angular/[email protected] #1104

alexandrearc opened this issue Jun 16, 2016 · 3 comments

Comments

@alexandrearc
Copy link

1.Environment:
Mac OSX El Capitan

  1. Versions.

Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.6
node: 4.4.5
os: darwin x64

  1. Repro steps.

$ ng new APP_NAME

  1. The log given by the failure. Normally this include a stack trace and some
    more information.

@angular/[email protected] postinstall: typings install
spawn ENOENT
Error: @angular/[email protected] postinstall: typings install
spawn ENOENT
at ChildProcess. (/usr/local/lib/node_modules/angular-cli/node_modules/npm/lib/utils/spawn.js:17:16)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:827:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

@RicardoVaranda
Copy link
Contributor

#1092 Duplicate entry of the same issue, problem is in typings install not router, you can manually fix it by running the following command from the project directory:

npm run postinstall

@filipesilva
Copy link
Contributor

I'm closing this one as a duplicate, but will continue addressing it in #1092.

@angular-automatic-lock-bot
Copy link

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 angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants