Sharing .npmrc between local build and production deploy

Support
,
1

Hi,

I am using .npmrc to authenticate for a private Github package.

In order for Netlify to access my auth token, I pass it into .npmrc like this:

@netlify:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${NPM_TOKEN}

However, when I build locally, I get the error

"Failed to replace env in config: ${NPM_TOKEN}"

Can anyone offer some advice on how to access environment variables locally using process.env and through Netlify using ${SOME_NETLIFY_VARIABLE} at the same time? Currently I have to manually edit the file between environments.

Thanks

2

If you use Netlify Dev, you should be able to use process.env.

3

Thanks @hrishikesh , Iā€™ll definitely look into that.

But is there a way to do it without using Netlify Dev? Iā€™m imagining thereā€™s some sort of logic saying something like ā€œif local, use the auth token on my machine, else if using Netlify, use the env variableā€

4

Well, in most Static Site Generators thereā€™s a way to differentiate between development and production builds, but since this part is not being managed by a SSG, Iā€™m not sure if conditional logic is possible here.

Maybe someone else can chip in.

5

maybe you could utilize context for this?

6

Contexts would be useful if the variables are different between production and development, if Iā€™m not wrong. But, in this case, the variables have the same value, itā€™s just a difference of how to access them in the code.