Thomas Watson
@watson.bsky.social
Computer programmer, Node.js Core member, open source hacker and Node.js dev at Datadog, formerly Elastic + Opbeat (acq)
What's going on with the `next` package and npm servers today?
All day our CI randomly gets these errors. But for some reason only for `next`. Any other npm package works fine. Re-run it a few times and the error goes away 🤔
status.npmjs.org is all green, but that page has never been reliable 🤷
All day our CI randomly gets these errors. But for some reason only for `next`. Any other npm package works fine. Re-run it a few times and the error goes away 🤔
status.npmjs.org is all green, but that page has never been reliable 🤷
January 8, 2025 at 11:55 AM
What's going on with the `next` package and npm servers today?
All day our CI randomly gets these errors. But for some reason only for `next`. Any other npm package works fine. Re-run it a few times and the error goes away 🤔
status.npmjs.org is all green, but that page has never been reliable 🤷
All day our CI randomly gets these errors. But for some reason only for `next`. Any other npm package works fine. Re-run it a few times and the error goes away 🤔
status.npmjs.org is all green, but that page has never been reliable 🤷
I was using Copilot today to write a bash script and I had an array of host names. It suggested this code - even added a nice copyright. Seems to come from this Node.js book: www.scribd.com/document/685...
November 18, 2024 at 10:43 PM
I was using Copilot today to write a bash script and I had an array of host names. It suggested this code - even added a nice copyright. Seems to come from this Node.js book: www.scribd.com/document/685...