Gregory's ServerCompare that to #Webpack, which has the same number of major releases, and we're looking at 606,25 days for a new release on average.
|
4 comments
 We should have a website that compares this metric for different kinds of software to make it easier to choose a tool that you don't have to touch every full moon. @garritfra The problem is that this metric isn't helpful for a single dep. What you need to know is the combined frequency of breaking changes for your entire dep tree. And even then, it matters whether deps are tightly coupled. For example, a dep that bumps major whenever Vite bumps major can be dealt with in one go, which is less disruptive than an uncoupled breaking change. @dpom I agree. I suppose this would only work for comparing major technologies, e.g. Vite vs. Webpack, React vs. Vue vs. Angular, Bootstrap vs. Tailwind, ... It's hard to automate this for every project on NPM (or other PMs). Of course this will never be exact, since each project has different policies of when and how they release major versions. But it could give you a hint of what to expect. |
In other words: A project using Vite needs attention more than twice as often as Webpack.