4 ms·
It feels like there are some inconsistencies in this article: * we're using projects internally and don't want the hassle of rewriting import paths when making
by room271 6y ago
It feels like there are some inconsistencies in this article:
* we're using projects internally and don't want the hassle of rewriting import paths when making backwards-incompatible changes
* we don't want to just give up on semver and publish breaking changing on the v0/1 numbering scheme
I feel like you have to pick one. If it's the first, then it's actually a positive thing that explicit import path rewrites are needed in my mind at least.