@forbeslindesay @iamstarkov not really. not when you have tons of integrations and dependents.
-
-
Replying to @sebmck
@sebmck@ForbesLindesay@iamstarkov maybe that’s a sign that having a single version number for all those packages is not a great idea?1 reply 0 retweets 1 like -
Replying to @MoOx
@moox@forbeslindesay@iamstarkov different package versions has way more issues1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@MoOx@ForbesLindesay you are saying this like@PostCSS, webpack and remark, gulp, grunt etc ecosystems are worse at handling this1 reply 0 retweets 0 likes -
Replying to @iamstarkov
@iamstarkov@moox@forbeslindesay they have less packages and less public api2 replies 0 retweets 0 likes -
Replying to @sebmck
@sebmck@MoOx@ForbesLindesay and gulp and grunt has dozens of packages1 reply 0 retweets 0 likes -
Replying to @iamstarkov
@iamstarkov@moox@forbeslindesay gulp has like 2 core packages, i'm not sure what parallels you're trying to draw1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@iamstarkov@MoOx Babel has about 4 core packages. The rest are just plugins that live in the Babel repo2 replies 0 retweets 1 like -
Replying to @ForbesLindesay
@forbeslindesay@iamstarkov@moox no it doesn't. babylon, babel-types, babel-generator, babel-core, babel-template, babel-traverse etc...1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@iamstarkov@MoOx Babel-template is just a shared helper used by a lot of plugins1 reply 0 retweets 0 likes
@forbeslindesay @iamstarkov @moox it's exposed from babel-core. there's also babel-helper-* of which there are 18 packages
-
-
Replying to @sebmck
@forbeslindesay@iamstarkov@moox just because they are used by plugins does not mean they aren't core0 replies 0 retweets 0 likesThanks. 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 