Quick Fix: Verdaccio Token CLI Warnings

[ianrohde]

Issue

I noticed these warnings and did a quick search on Phind. One of the last recommendations was to remove the curly braces around the variable name.

When using environment variables in the .npmrc file, make sure to use the variable name without curly braces. For example, use $NPM_TOKEN instead of ${NPM_TOKEN}. stackoverflow.com

I tried it. It worked.

Details

Before

After

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-commerce	❌ Failed (Inspect)			Sep 28, 2023 0:26am
react-commerce-prod	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 28, 2023 0:26am

[federicobadini]

If you run on Vercel purging the cache you receive a 401.
We attempted the same on another .npmrc variable: #1758
Since it was a minor I did not spent so much on it though. So maybe there is a slightly different solution that works. But I suspect that just removing the parenthesis doesn't

[ianrohde]

I don't have Vercel access to react-commerce, so pardon me if this is already in use or tested, but it looks like these are supposed to be managed through the Environment Variables UI, then called with process.env.

Next.js has built-in support for loading environment variables from .env.local into process.env.

(link)

I've tried using process.env before here, but we had to revert. It may have been due to the same 401 issue you saw. It's odd to me that using a simple variable is such an issue when it's supposed to be supported 🤷