[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Discussions](/c/community/4) # NPM_RC token in v0? 104 views · 1 like · 6 posts Simon (@simonstrumse) · 2025-06-15 What does it mean when chat asks me to input environment variables for nmp_rc and npm_token When i don't I get this in console but everything seems to work fine. NPM_RC cannot be accessed on the client. 18:23:31.670Z NPM_TOKEN cannot be accessed on the client. Is this something I should need to configure at all in this setup, or is the system a bit confused? Pauline P. Narvas (@pawlean) · 2025-06-20 Hey, Simon! Great question. Let me try and get an answer from the team. However, I've not seen this issue before - do you happen to have a chat example where you've seen this? There shouldn't be anything you need to configure. Simon (@simonstrumse) · 2025-06-22 yes I can DM anyone in your dev team a private link to the chat if they want to see. Its in the list of a few ENVs the system sometimes asks for. I think they are like: Vercel_url, next_public_url and a now this one, which when I research them are all supposed to be set by vercel in the system. It works just ignoring them, but it is confusing in the dev process. Simon (@simonstrumse) · 2025-06-22 this is how it looks like in chat  Jacob Paris (@jacobparis) · 2025-06-24 · ♥ 1 Those should only appear there if they're detected in the codebase, is it possible any of your scripts has referenced them? Simon (@simonstrumse) · 2025-06-28 the problem of asking a vibecoder.... v0 wrote all and any kind of reference in there. I tried to instruct it to look for them and remove the references if they are there, but it seems very persistent.
