Operating with my own exclusive Gemfury repository, I am actively releasing npm packages.
Intrigued by the prospect of applying distribution tags to my packages (as per this guide: https://docs.npmjs.com/cli/dist-tag).
The configuration of my npm registry points to a proxy that facilitates installations from both my private repository and the public npm registry. Not only can I install from my private registry effortlessly, but also publish to it without any hitches.
An attempt at executing npm view on my privately-packaged product yields all expected information seamlessly.
However, upon trial of any npm dist-tag commands, setbacks arise. A mere 404 Not Found error message surfaces from npm.
Here's what happens:
npm dist-tag ls my-private-package-name
yields:
npm ERR! dist-tag ls Couldn't get dist-tag data for my-private-package-name
npm ERR! Darwin 16.4.0
npm ERR! argv "/Users/me/.nvm/versions/node/v4.2.6/bin/node" "/Users/me/.nvm/versions/node/v4.2.6/bin/npm" "dist-tag" "ls" "my-private-package-name"
npm ERR! node v4.2.6
npm ERR! npm v2.14.12
npm ERR! code E404
npm ERR! 404 Not Found : MyPriVaTeGemfuryToKEn
npm ERR! 404
npm ERR! 404 'MyPriVaTeGemfuryToKEn' is not in the npm registry.
npm ERR! 404 Your package name does not meet the requirements, as
npm ERR! 404
npm ERR! 404 1. Names are no longer allowed to contain capital letters
npm ERR! 404
npm ERR! 404 Note that you have various installation options such as using a
npm ERR! 404 tarball, directory path, http link, or git URL.
Weirdly enough, no typos here. The situation seems peculiar. This anomaly persists across all dist-tag commands. Oddly, the error appears to incorporate my private Gemfury token as the package name. However, the initial line of the issue report seems accurate. It could be construed as an aberration in the error messaging system; yet the crux of the matter remains: I'm unable to employ any dist-tag directives on a package within my secluded registry. Is there something crucial missing from my approach?