Npm package under organization (solved)

Gitea Usages
1

I am attempting to publish an npm package into a private organization, but am struggling.

Following the gitea instructions I now have a revised .npmrc file using the “npm config set” calls suggested.

One confusing part is the {token} mentioned in the docs. Where does that come from? My assumption was the application token that we can generate, which is what I used.

Another assumption from the docs was that the {owner} can be replaced by the organization code.

The result experienced is always the same

npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in to https://mygitdomain.tld/api/packages/myorg/npm/
npm ERR! need auth You need to authorize this machine using `npm adduser`

What am I missing or misunderstanding here?

2

Of course I figured it out right after posting the question. However, the answer may be good to update the documentation.

It was in the .npmrc file

registry=https://mygitdomain.tld/api/packages/myorg/npm/
//mygitdomain.tld/api/packages/myorg/npm/:_authToken={application_token}
//mygitdomain.tld/api/packages/npm/:_authToken={application_token}

The trick was a second auth line without the username/organization in the path.