npm -g i npm@v1.4 installs from v1.4-next

[mgol]

$ npm --version
1.4.26
$ npm info npm dist-tags

{ latest: '2.0.0-beta.0',
  'v2.0rc': '2.0.0-beta.0',
  next: '2.0.0-beta.2',
  'v1.4-next': '1.4.26',
  'v2.0-next': '2.0.0-beta.2',
  'v1.4': '1.4.25' }

$ npm -g i npm@v1.4
/Users/mgol/.nvm/v0.11.13/bin/npm -> /Users/mgol/.nvm/v0.11.13/lib/node_modules/npm/bin/npm-cli.js
npm@1.4.26 /Users/mgol/.nvm/v0.11.13/lib/node_modules/npm
$ npm --version
1.4.26

I'm on OS X 10.9.4, Node.js installed via nvm.

[othiym23]

Confirmed, but this is really a bug in how we're using tags: node-semver treats v1.4 as 1.4 as 1.4.x, so it's installing the newest version of 1.4 and not the dist-tag. We'll come up with a new way to tag these things, and leaving this issue open to track that.

[isaacs]

Best suggestion is probably to have the client refuse to tag things with a tag name that is a valid semver range. After a year or two of that in the client, we can enforce on the server.

[mgol]

We publish the jQuery 1.x branch under the 1.x tag, IIRC that was your recommendation, @isaacs. It was supposed to look at tags first and only afterwards at semver ranges, wasn't it? cc @scottgonzalez @dmethvin

What will happen to existing semver-range-like tags? Will we be able to unpublish them with the new npm?

[smikes]

What will happen to existing semver-range-like tags? Will we be able to unpublish them with the new npm?

Yes, this is now supported as of npm@2.5.0 -- you can remove dist-tags with

npm dist-tag rm jquery 1.x