3 ms·
Looking at the actual specification ( https://semver.org/ https://semver.org/ ): > 1. Software using Semantic Versioning MUST declare a public API. This API co
by yawaramin 8y ago
Looking at the actual specification ( https://semver.org/ https://semver.org/ ):
> 1. Software using Semantic Versioning MUST declare a public API. This API could be declared in the code itself or exist strictly in documentation. However it is done, it should be precise and comprehensive.
I don't believe we can make such a claim about Prettier's output format. For example, how would you denote a backward-compatible change to the output format?
- baddox 8y agoPrettier has a clear API. That’s my point: there by definition cannot be backwards-compatible changes to the output format.
- yawaramin 8y ago> there by definition cannot be backwards-compatible changes to the output format. In that case we can conclude that it's incompatible with SemVer! SemVer is all about trying to convey what changes to a package are backward-compatible and thus are safe to upgrade to new versions. The whole point is that you can say something like "that-package": "^3.9.1" and mean that you're OK to upgrade up to anything less than 4.0.0. If you can never do that, the package is obviously not using SemVer.