Re:Webpack 3: Official Release
by skrebbel on Tuesday June 20, 2017 @04:16AM
(#14592913)
In semver land, every major release is a tragedy. I love that they're really doing hard (and free!) work to make the transition as smooth as possible, but I still wish the JS ecosystem culture would be more conservative about releasing breaking changes.
[ Parent
| on HN ]
Re:Webpack 3: Official Release
by coffeedoughnuts on Tuesday June 20, 2017 @04:37AM
(#14592977)
From the article:
Migrating from webpack 2 to 3, should involve no effort beyond running the upgrade commands in your terminal. We marked this as a Major change because of internal breaking changes that could affect some plugins. So far we’ve seen 98% of users upgrade with no breaking functionality at all
Your point being? The plugin interface is a public interface too, right?
Again, I really appreciate all the work done to make this smooth, but there's still a little underlying "compatibility matters less than features" sentiment here.
> The plugin interface is a public interface too, right?
It didn't say 'plugin interface'. It said 'internal changes' that could affect some plugins. The way I read that is some plugins could be relying on internals (that they technically shouldn't, they may have good reason ofc).