TIL: @babeljs does not follow SemVer (https://github.com/babel/babel/blob/master/CHANGELOG.md …) breaking changes can happen in any version!
-
-
-
Replying to @sebmck
@ForbesLindesay wait are you referring to 6.4.0? That shouldn't be labelled a breaking change, it wasn't.3 replies 0 retweets 1 like -
Replying to @ForbesLindesay
@forbeslindesay do you consider all bug fixes to be breaking changes?1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@ForbesLindesay if people already rely on this bug, then yes2 replies 0 retweets 0 likes -
Replying to @iamstarkov
@iamstarkov@sebmck if it is easy to be unaware of the bug, but dependent on the buggy behaviour, yes1 reply 0 retweets 0 likes -
Replying to @ForbesLindesay
@forbeslindesay@iamstarkov it's easy to dependent on any bug2 replies 0 retweets 0 likes -
Replying to @sebmck
@forbeslindesay@iamstarkov also what if not fixing a bug allows others to exist. illegal nodes being allowed in places has consequences1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@iamstarkov just release a major version. Numbers are cheap.1 reply 0 retweets 0 likes
@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 - 9 more replies
New conversation -
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 