npm install error

[leowidodo]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

How can the CLI team reproduce the problem?

42506 error Windows_NT 10.0.15063

42507 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
42508 error node v6.11.2
42509 error npm v3.10.10
42510 error code ELIFECYCLE
42511 error angular2-quickstart@1.0.0 postinstall: typings install
42511 error Exit status 1
42512 error Failed at the angular2-quickstart@1.0.0 postinstall script 'typings install'.
42512 error Make sure you have the latest version of node.js and npm installed.
42512 error If you do, this is most likely a problem with the angular2-quickstart package,
42512 error not with npm itself.
42512 error Tell the author that this fails on your system:
42512 error typings install
42512 error You can get information on how to open an issue for this project with:
42512 error npm bugs angular2-quickstart
42512 error Or if that isn't available, you can get their info via:
42512 error npm owner ls angular2-quickstart
42512 error There is likely additional logging output above.
42513 verbose exit [ 1, true ]

supporting information:

• npm -v prints:
• node -v prints:
• npm config get registry prints:
• Windows, OS X/macOS, or Linux?:
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.