Hacker News new | ask | show | jobs
by peterbe 1774 days ago
(author here) We're still on FlexSearch 0.6 and the new 0.7 is a big refactor. I hope we can upgrade some time.
1 comments

Any reason for not using semantic versioning?

I see in your npm page that despite compatibility "some adjustments" might be needed, aka you broke compatibility. If you did a breaking change, you need to up that major version my man.

Please stop with this sentimental versioning, it just causes issues for the rest of us who want to rely on npm's ability to not upgrade stuff on breaking changes, now everyone's gonna have to lock you package version to 0.6 so they don't get your breaking stuff from 0.7.

Semver allows for breaking changes with major version 0: https://semver.org/#spec-item-4