@amasad OTOH increased chance that unintended breaking change will be reported (because more users) and next patch will fix it for everybody
-
-
Replying to @dan_abramov
@dan_abramov that's true, but is there a way to do this more responsibly? Have it be opt-in rather than the default?1 reply 0 retweets 0 likes -
Replying to @dan_abramov
@dan_abramov yeah maybe that's true, although they might be a minority given how many people get affected by babel's breaking bug fixes2 replies 0 retweets 1 like -
Replying to @amasad
@amasad why doesn't Babel just bump majors more often?@dan_abramov1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo@amasad@dan_abramov we will probably have to in the future. just need to get the infra in place to do it.1 reply 0 retweets 1 like -
Replying to @sebmck
@lbljeffmo@amasad@dan_abramov the problem is we have so many integrations that people use. keeping them on old versions isn't good.1 reply 0 retweets 0 likes -
Replying to @sebmck
@lbljeffmo@amasad@dan_abramov there's also projects who directly expose babel and depend on it like systemjs/electron/atom.1 reply 0 retweets 0 likes -
Replying to @sebmck
@lbljeffmo@amasad@dan_abramov so they need to bump majors when we do, which means they could be on old versions for a long time2 replies 0 retweets 0 likes -
Replying to @sebmck
@lbljeffmo@amasad@dan_abramov well have to figure out some way to coordinate with the projects that expose babel to match their rel. cycle1 reply 0 retweets 0 likes
@lbljeffmo @amasad @dan_abramov and figure out some way to autoupdate integrations through a script or by moving them into the monorepo
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 