Official @npmjs support is here to help! No DMs, please. Need help? Visit https://xitter.cf/t.co/itIpSbF82w.
Joined February 2014
- Tweets2.4K
- Following25
- Followers1.7K
- Likes25
npm support retweeted
[status] Resolved: This incident has been resolved. stspg.io/wjjt0jx0ss5w?u=1vl7…
npm support retweeted
[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=3xt1…
npm support retweeted
We're live with @npmjs's Open RFC Call youtube.com/watch?v=tuTT9GYD…
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
npm support retweeted
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
npm support retweeted
[status] Resolved: The APIs remain stable and all systems are back to normal. We're resolving this incident. stspg.io/89de28590
npm support retweeted
some users are experiencing difficulty accessing scoped packages and some features of the npm website. more information is available here: status.npmjs.org/incidents/q…
npm support retweeted
[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
npm support retweeted
[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
npm support retweeted
[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
npm support retweeted
[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
npm support retweeted
[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
npm support retweeted
[status] Resolved: This incident has been resolved. stspg.io/2b48884b6
oooooh. much like. see thread for all the shiny. : ) xitter.cf/seldo/status/976568040…
npm support retweeted
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/releases/…
npm support retweeted
[status] Identified: The packages `package`, `delete`, and `dumbledore` are currently unavailable. We have identifi… stspg.io/4bceb2ca9
npm support retweeted
[status] Monitoring: We believe all cleanup is complete, and all packages are back to the state they were in before… stspg.io/8565d80e5
npm support retweeted
[status] Identified: We have restored all the package-versions for the 9 packages that were published over. We are … stspg.io/8565d80e5