[ChiperSoft]

> read any of the versioning like bower does, so it can't handle versioning properly

What would the "proper" behavior be? How would npm know which commit is the one you intended to be the version change? Scan the history of package.json and only grab the commit when the version number changed?

Isn't that entirely the point of using tags?

[Touche]

NPM doesn't use tags to do semver comparisons. To NPM a tag is no different than a branch or a commit hash. This differs from Bower and half dozen other package managers that do semver against tags.

[ChiperSoft]

Bower has a backend that is reading the git repo and converting tags into semver versions. They automated NPMs publishing process. Doing this in realtime in the NPM client would be very time consuming.

[BinaryIdiot]

> Doing this in realtime in the NPM client would be very time consuming.

Nonsense; this is a very quick operation in git. Even in enterprise situations you're probably not going to have a huge amount of private repositories.