What an asinine interpretation. No thanks.

Care to explain why you do believe it is "an asinine interpretation"?

I agree. It's up to the publisher to decide the significance of version numbers. Just because Node does it one way doesn't mean everyone else has to follow suit.

The entire NPM ecosystem is based on semver.

That’s the sole reason for the squiggly marks and carets that exist in every package.json.

Dismissing the very rule package.json is written in just because you don't know what it is?

I'm not the one talking about "package.json." We're talking about software version numbers.