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
@sebmck Or can you publish in topo order?@ArnaudRinquin@maybekatz1 reply 0 retweets 0 likes -
Replying to @sophiebits
@soprano@arnaudrinquin@maybekatz There are circular dependencies so it's not a complete solution unfortunately.1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@ArnaudRinquin@maybekatz :o you can do that??1 reply 0 retweets 0 likes
@soprano @arnaudrinquin @maybekatz Yeah, babel-types and babel-traverse both depend on each other. I dunno how npm deals with it... Magic...
-
-
Replying to @sebmck
@sebmck@soprano@ArnaudRinquin@maybekatz pin them each to staggered versions and see if the universe implodes.0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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 