The npm blog has been discontinued.
Shutting Down #npm IRC
#npm channel on irc.freenode.net is being devoiced. That means: if you’re not a moderator in the channel, you won’t be able to post there. Instead, you’ll be redirected to this message.
As an official communication channel, IRC is difficult for us to adequately moderate and maintain. A welcoming and compassionate npm community is important to us, and as a small team, moderating IRC effectively has proven very difficult. Since
#npm is probably always going to be seen as an “official” npm venue, we cannot in good conscience continue to let it fall into disrepair.
Here are some much better places to seek help, guidance, and support, which are actively moderated and maintained, either by us or by others.
- If you’re experiencing service issues, check https://status.npmjs.org to see if it’s a known issue being worked on.
- npm.community is the best place to seek support. If you’re in doubt, we’re here to help. This is also the best place to report bugs and request features.
- If that fails, you can reach out to email@example.com to talk to us about your npm problems.
- You can hit us up on Twitter at @npm_support with questions, at @npm_hiring for recruitment updates, at @npmstatus for operational status updates, or at @npmjs with puns and wombat pictures.
- package.community is a Discord chat server with channels dedicated to discussions of package management in general, as well as npm issues specifically.
- /r/npm on Reddit is a place where people share cool modules they’ve written and ask questions about various things.
- If you’re really committed to using good old fashioned IRC, the
#npmchannel, we won’t stop you, but we also can’t commit to helping you moderate it.
edited 2018-09-11 by isaacs to add links to npm.community