All of the changes that I've listed introduce backwards non-compatible changes
Sure, but they don't all introduce public api changes and that's the point, semver only speaks to the public api.
While whatever I typed in the codebase may not change the API as it appears in the source code, the transpiled version of the code now includes API changes
Ah, as I said, node/javascript ecosystem is not my main area of expertise, so fair enough, my bad.
They are part of the contract that guarantees the integrity of the API
Ok, but that isn't the same thing as being part of the public api.
FYI, we are not the first to have this debate. There is a long, ongoing debate in the semver repository on exactly this subject.
Thanks for the link, it's an interesting debate, but it's ultimately moot. The spec says what the spec says and no where does the spec mention supported platforms being part of the public api, so it isn't part of the public api. Maybe that will change in semver 3.0.0, but as it stands, it is what it is or isn't what it isn't, as the case may be.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sure, but they don't all introduce public api changes and that's the point, semver only speaks to the public api.
Ah, as I said, node/javascript ecosystem is not my main area of expertise, so fair enough, my bad.
Ok, but that isn't the same thing as being part of the public api.
Thanks for the link, it's an interesting debate, but it's ultimately moot. The spec says what the spec says and no where does the spec mention supported platforms being part of the public api, so it isn't part of the public api. Maybe that will change in semver 3.0.0, but as it stands, it is what it is or isn't what it isn't, as the case may be.