RF: release channels

[Vojta Jina]

I think it might be helpful to have multiple release channels.

You can already achieve it by:

npm publish // publishing new v1.0.1
npm tag some@1.0.0 latest
npm tag some@1.0.1 canary

Then people can install canary release by:

npm install -g some@canary

I think it might be helpful to have better support for this scenario:

• add argument to publish (which channel, the default would be latest)
• display available channels on npmjs.org package info
• installing some@canary would mean, that npm update keeps updating from canary channel

[isaacs]

That already works, exactly how you describe it.

[isaacs]

Also, you can do it in one step, if you like:

npm publish --tag canary

# then later...
npm tag some@1.2.5 stable