Having trouble with bit install about bit

[itaymendel]

a valid .npmrc should look similar to this; it has a line for your organization as a scoped-registry and a line defining the token for authentication.
if you move from node.bit.cloud to node-registry.bit.cloud, please also delete your lock-file, as sometimes it contains references to the registry url, so it needs to be re-evaluated:

@bitdev:registry=https://node-registry.bit.cloud
@teambit:registry=https://node-registry.bit.cloud
@YOUR-ACCOUNT:registry=https://node-registry.bit.cloud
//node-registry.bit.cloud/:_authToken=TOKEN

[benjgil]

HI @murm
It seems you dont have the npmrc config for installing @teambit packages.
Please run the following to add it:
npm config set '@teambit:registry' https://node-registry.bit.cloud

[artem-zaiko-yara]

bump

[artem-zaiko-yara]

Try to get auth token with bit config get user.token

and then set it in .npmrc

//node-registry.bit.cloud/:_authToken=<token>
//node.bit.cloud/:_authToken=<token>

[NikitaRogozhyn]

Hi everyone

I'm facing the same issue right now.
I've tried to do these steps @benjgil @artem-zaiko-yara but it doesn't help. I've also recovered the approach from the official documentation https://bit.dev/reference/packages/npmrc but it doesn't work as well.

[albertovaccarella]

Same issue when deploying one of my apps to heroku, which I configured with an .npmrc as per docs (pointing to node-registry.bit.cloud). Then I deployed an older app, which I haven't updated in a bit and still has the old registry url (node.bit.cloud) and it worked: I then changed the first app's .npmrc to point to node.bit.cloud too and the build succeeded...
In other words, it seems like the registry URL keeps changing back and forth from node-registry.bit.cloud to node.bit.cloud, or am I missing something?

[benjgil]

All these issues are almost certainly because your npmrc only contains a token for node.bit.cloud, but not for node-registry.bit.cloud

Just adding an entry telling bit to look for scoped packages in node-registry.bit.cloud isnt enough, you need to also provide a token for that registry

Note to all - this will be managed better automatically by bit from the next stable version of bit, which will automatically set and update tokens for bit registries (as it used to do until around nov 23)