The npm blog has been discontinued.
Where to get help from npm
We know there are a multitude of npm issues our users deal with every day, and a bunch of different ways to get in touch with us, so we thought it would be useful to have a single list to help you decide the best way to reach us. So here’s all the ways you can talk to us, and what they’re good for:
- Questions about installing, publishing, error messages, account access, package name disputes, and any issues with Private Modules, npm On-site, or npm Organizations.
- When in doubt, you can always email npm support!
- npm/npm/issues on GitHub
- npm command-line interface (CLI) bugs, CLI error messages, feature requests or pull requests for the CLI team
- Please include the npm-debug.log in gist form when requesting help decoding error messages
- npm/newww/issues on GitHub
- Bugs, feature requests, or pull requests for the website
- Asking for more details on npm job postings, submitting your job application
- Inquiring about featuring your company’s job postings on our Who’s Hiring page and sidebars.
- Any issues (+ evidence/data) you’ve noticed with registry security &/or website security
- When you really, really don’t think any of the ones above match what you have to say.
- @npm_support on Twitter
- Tweet-sized issues that can (probably) be solved with tweet-sized responses
- @npmjs on Twitter
- Voicing concerns that don’t necessarily need a response, such as registry status updates, & sharing your love of npm with the world!