Version-Numbers are sorted lexically? alpha9 ist "newer" than alpha31

[ottes]

We saw this, when installing https://www.npmjs.org/package/zombie

Via Sinopia Version 2.0.0-alpha9 is installed, without it 2.0.0-alpha31 will be used.

I guess this is not the behaviour it should be, right?

[rlidwka]

I guess this is not the behaviour it should be, right?

Bad guess. :)

It seems to be a correct behaviour.

version 2.0.0-alpha9 is installed, without it 2.0.0-alpha31 will be used.

Sinopia is using semver sort provided by semver package. But it's the same algorithm npm itself is using. For example, npm install 'zombie@<2.0.0-alpha10' will install 2.0.0-alpha1, not 2.0.0-alpha9 as you would expect.

Note that 2.0.0-alpha9 is considered greater than 2.0.0-alpha31, but 2.0.0-alpha.9 is lower than 2.0.0-alpha.31:

> require('semver').compare('2.0.0-alpha9', '2.0.0-alpha31')
1
> require('semver').compare('2.0.0-alpha.9', '2.0.0-alpha.31')
-1

So you might consider filing a bug report against zombie package asking to change their alpha numbering system.

[ottes]

I will do this.... but one question is open: why is it working with npm directly, but not with sinopia? is it possible to "stick" the version on sinopa site, not on my package.json ?

[rlidwka]

why is it working with npm directly, but not with sinopia?

It works with npm because "latest" tag is set. Sinopia ignores this tag for a number of reasons, but it might be changed in the future.

[rlidwka]

Starting from [email protected], behaviour of "latest" tag is consistent with npm registry. So, it should work now.

closing as duplicate of #50