README should explain what to do about "authentication token not provided" during npm install

[pdurbin]

The first command in the README (npm install) fails with this:

npm ERR! 401 Unauthorized - GET https://npm.pkg.github.com/download/@IQSS/dataverse-client-javascript/2.0.0-pr67.5dfc70a/dc27a9a220a347fb9e5d87f6887c8e87427482c1 - authentication token not provided

We should update the README to explain what to do.

Some notes:

read:packages

https://iqss.slack.com/archives/C04MJ76A34Z/p1685557309486369?thread_ts=1685556469.110549&cid=C04MJ76A34Z

[pdurbin]

This is what worked for me:

cp .npmrc.example .npmrc

Then edit and fill in YOUR_GITHUB_AUTH_TOKEN with a classic token you create with read:packages. See https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#authenticating-to-github-packages

I didn't set up YOUR_NPM_AUTH_TOKEN. I don't think I need it.

legacy-peer-deps=true

# design-system registry
//registry.npmjs.org/:_authToken=<YOUR_NPM_AUTH_TOKEN>
@iqss:registry=https://registry.npmjs.org/

# js-dataverse registry
//npm.pkg.github.com/:_authToken=<YOUR_GITHUB_AUTH_TOKEN>
@iqss:registry=https://npm.pkg.github.com/

[aadorian]

registry.npmjs.org/:_authToken=<YOUR_NPM_AUTH_TOKEN

I have the same issue, and solve it commenting with hashtag # the registry lines #registry.npmjs.org/:_authToken=<YOUR_NPM_AUTH_TOKEN

[pdurbin]

@aadorian thanks. Do you think the README is fine as-is? if not, are you interested in making a pull request?