Thank you for the suggestion. I finally got it working.
Looks like I messed up the
file by trying to set the registry, since the documentation did not say anything about private packages being stored the same place as public. I deleted the registry line, and things started working.
Yes, I did a
, but did not see any documentation about needing a login and it did not help because the messed up
trying to set the registry.
Q: I see a boatload of tokens on https://www.npmjs.com/settings/johngrabner/tokens
A token is generated every time I log in? Do these ever expire or do last accumulate over time and last forever?
Q; is there where I can make suggestions for the documentation? If so,
Line “If you wish, you may associate a scope with a registry; see below.”
Add “This is not necessary for private packages hosted by npm”
Line " You can then change the access permissions, if desired, with
npm access or on the npmjs.com website."
Add "Alternatively, to post to your private scope, make sure the name in package.json included your scope as in @blawblaw/mypackage, then npm login, and npm publish.
add “not required for npm Orgs private packages”
Line: “Installing scoped packages”
add "Must have an auth token in the ~/.npmrc file before issuing these commands. The easiest way to add this token is to issue the “npm login” command