registry overrides should only within the semver range about registry HOT 5 CLOSED

Let's make this the ~ range and not semver range.

from registry.

This is implemented to the semver range within the CLI now. The CDN needs to be updated next.

from registry.

at the very bottom of the readme over at https://github.com/jspm/registry it says ...
The overrides only apply to exact version, tag or branch names. When set to an exact semver version, the override will apply for all semver versions greater than that version.

now I installed jspm install [email protected] but the existing override [email protected] seems to not being effective in this case.

Is this due to the existence of [email protected] or is there something I missed that still needs to be implemented?

from registry.

For 0.0 versions, the semver range is exactly that version only! npm have been needing to communicate these ideas recently themselves, so it is not widely known (yet). https://github.com/npm/node-semver#caret-ranges-123-025-004

from registry.

thanks a lot for pointing this out!

On Tuesday, September 23, 2014, Guy Bedford [email protected]
wrote:

For 0.0 versions, the semver range is exactly that version only! npm have
been needing to communicate these ideas recently themselves, so it is not
widely known (yet).
https://github.com/npm/node-semver#caret-ranges-123-025-004

—
Reply to this email directly or view it on GitHub
#11 (comment).

from registry.