So, I’m trying to make sure that both of my dist-tags constantly work. I have been publishing
-pre.X releases under the dist-tag
$ npm dist-tag ls latest: 0.98.0 next: 0.99.0-pre.11
Now, I tried to publish under a new release version:
$ npm version minor -sm "(rel) v%s" v0.99.0 $ npm publish --tag latest --tag next + @email@example.com
Unfortunately, it doesn’t look like you can
publish under multiple dist-tags at once:
$ npm dist-tag ls latest: 0.98.0 next: 0.99.0
Worse, I don’t seem to be able to update it:
$ npm publish --tag latest npm ERR! publish Failed PUT 403 npm ERR! code E403 npm ERR! You cannot publish over the previously published versions: 0.99.0. : @scope/project $ npm dist-tag add @firstname.lastname@example.org latest npm ERR! code E401 npm ERR! Registry returned 401 for PUT on https://registry.npmjs.org/-/package/@scope%2fproject/dist-tags/latest
What do I do to update my
Some other feedback:
dist-tagbadly needs some additional documentation. I can’t figure out how it’s intended to be invoked!
npm publishshould probably support multiple
--tagarguments? I see a lot of packages with out-of-date dist-tags, i.e. a
@nexttag that is still pointing to a prerelease of a version three major versions ago …
This forum format is horrible. There, I said it. I mean, I love y’all (at least, those of you which I’ve met at the various conferences) … but I haven’t been forced to use a piece of terrible forum software like this since, I dunno, 2008? Why the reversion to terrible, user-hostile, Past Technology?
None of my business, I suppose; just thought the additional feedback might contribute to others’ complaints.