Of course as soon as I release a new version of my package, @babeljs decides its latest version is no longer gonna be npm-installable. wtf
-
-
Replying to @zkat__
@maybekatz I underestimated how slow npm publish is and how many packages I had to publish over hotel wifi.4 replies 0 retweets 5 likes -
Replying to @sebmck
@sebmck@maybekatz Ah, I was wondering about this. It seems like a lot of work. Good luck!1 reply 0 retweets 0 likes -
Replying to @ArnaudRinquin
@arnaudrinquin@maybekatz It's all automated. It's just taking forever because there are 50+ packages to update.pic.twitter.com/sox8kP7m2o
2 replies 0 retweets 0 likes -
Replying to @sebmck
@sebmck Maybe less racy if you push first with a tag, then set to 'latest' after?@ArnaudRinquin@maybekatz2 replies 0 retweets 0 likes
Replying to @sophiebits
@soprano @arnaudrinquin @maybekatz Yeah that's what I've settled on. I still need to test but I think npm tags are the solution.
12:12 PM - 11 Nov 2015
0 replies
0 retweets
1 like
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.
he/him 