npm support @support_npm

Official @npmjs support is here to help! No DMs, please. Need help? Visit https://t.co/itIpSbF82w. npmjs.com/support Joined February 2014

Tweets

2K
Followers

2K
Following

26
Likes

25

npm status @npmstatus

5 years ago

[status] Resolved: This incident has been resolved. stspg.io/wjjt0jx0ss5w?u…

1 4 2 0 0

[status] Scheduled (Jun 30, 2020, 00:00 UTC): npm will be performing planned maintenance on our databases for approximately 45 minutes. During this time you will not be able to publish packages. Apologies for the inconvenience. … stspg.io/fkhmrs2qy20r?u…

1 4 5 0 0

Darcy Clarke @darcy

6 years ago

We're live with @npmjs's Open RFC Call youtube.com/watch?v=tuTT9G…

0 2 4 0 0

npm support @support_npm

6 years ago

We're currently getting a high amount of spam into our support inbox, in our attempts to filter out the spam, we mistakenly bulk closed a number of your open tickets, we will re-open all of them as soon as possible and continue to answer your questions

1 3 3 0 0

npm @npmjs

7 years ago

we need your help to make npm and javascript even better. take a few minutes to complete the 2018 javascript ecosystem survey: buff.ly/2FUS29H

1 21 24 0 0

npm status @npmstatus

7 years ago

[status] Resolved: The APIs remain stable and all systems are back to normal. We're resolving this incident. stspg.io/89de28590

1 4 5 0 0

npm @npmjs

7 years ago

some users are experiencing difficulty accessing scoped packages and some features of the npm website. more information is available here: status.npmjs.org/incidents/qc6h…

1 4 4 0 0

npm status @npmstatus

7 years ago

[status] Monitoring: Some users are having trouble accessing npm registry services, or receive certificate errors, because of issues connected to an earlier DNS migration. We have updated nameserver (NS) settings in a way that should address this for al… stspg.io/051cedcba

1 1 3 0 0

npm status @npmstatus

7 years ago

[status] Investigating: We are receiving reports that new publishes are returning 500 status errors, with little more information as to why. It appears that packages are published as we are both seeing new publishes coming through and users report subs… stspg.io/e00c5dd5a

2 3 4 0 0

npm status @npmstatus

7 years ago

[status] Resolved: We have now invalidated all npm tokens issued before 2018-07-12 12:30 UTC, eliminating the possibility of stolen tokens being used maliciously. This is the final immediate operational action we expect to take today. We will be conduc… stspg.io/99e856545

1 21 17 0 1

npm status @npmstatus

7 years ago

[status] Monitoring: To protect potentially compromised accounts, npm is invalidating all npm login tokens created between 2018-07-11 00:00 UTC and 2018-07-12 12:30 UTC (about 2 hours ago). If you believe your account specifically was compromised we sti… stspg.io/99e856545

3 19 2 0 0

npm status @npmstatus

7 years ago

[status] Investigating: Our public packages replication host, replicate.npmjs.com, is experiencing high load from couchdb view generation. This is causing it to respond slowly or not at all to requests to replicate data. We are investigating mitigat… stspg.io/57e724aca

1 1 0 0 0

npm status @npmstatus

7 years ago

[status] Resolved: This incident has been resolved. stspg.io/2b48884b6

4 3 6 0 0

npm support @support_npm

8 years ago

oooooh. much like. see thread for all the shiny. : )

Laurie Voss @seldo

8 years ago

oooooh. much like. see thread for all the shiny. : )

19 118 524 0 1

Download Image

0 0 2 0 0

npm @npmjs

8 years ago

we’ve reverted a patch that could cause ownership changes on some system files. if you run npm@next, run `npm install -g npm@next` to get the fix: github.com/npm/npm/releas…