|
|
|
|
#### 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?
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
Please a complete description of how to reproduce the problem.
|
|
|
|
|
Include a gist of your npm-debug.log file.
|
|
|
|
|
If you've never used gist.github.com, start here:
|
|
|
|
|
https://github.com/EmmaRamirez/how-to-submit-your-npm-debug-log
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
### 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).
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
Thank you for contributing to npm! Please review this checklist
|
|
|
|
|
before submitting your issue.
|
|
|
|
|
|
|
|
|
|
- Please check if there's a solution in the troubleshooting wiki:
|
|
|
|
|
https://github.com/npm/npm/blob/latest/TROUBLESHOOTING.md
|
|
|
|
|
|
|
|
|
|
- Also ensure that your new issue conforms to npm's contribution guidelines:
|
|
|
|
|
https://github.com/npm/npm/blob/latest/CONTRIBUTING.md
|
|
|
|
|
|
|
|
|
|
- Participation in this open source project is subject to the npm Code of Conduct:
|
|
|
|
|
https://www.npmjs.com/policies/conduct
|
|
|
|
|
|
|
|
|
|
For feature requests, delete the above and uncomment the section following this one. But first, review the existing feature requests
|
|
|
|
|
and make sure there isn't one that already describes the feature
|
|
|
|
|
you'd like to see added:
|
|
|
|
|
https://github.com/npm/npm/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+label%3Aalready-looked-at
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
|
|
|
|
|
#### What's the feature?
|
|
|
|
|
|
|
|
|
|
#### What problem is the feature intended to solve?
|
|
|
|
|
|
|
|
|
|
#### Is the absence of this feature blocking you or your team? If so, how?
|
|
|
|
|
|
|
|
|
|
#### Is this feature similar to an existing feature in another tool?
|
|
|
|
|
|
|
|
|
|
#### Is this a feature you're prepared to implement, with support from the npm CLI team?
|
|
|
|
|
|
|
|
|
|
-->
|
