something changed in the node ecosystem that broke all our (thankfully staging) builds today but only discovered it about an hour ago and on a plane… rly looking fwd to spending my late evening triaging, fixing and then blameless rage tweeting the problem/resolution tonightpic.twitter.com/sG0Kvj9svG
-
Show this thread
-
without speculating too much I suspect it was a semver violation wherein an exuberant downstream dep used a syntax or semantics only available to node10
5 replies 0 retweets 2 likesShow this thread -
-
-
Replying to @DavidWells @southpolesteve
it is fully my fault for having our ci use npm@latest / should know better!
2 replies 0 retweets 2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.