Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 1 of 5

Github Package Registry scope conflict with proxy

Solved! Go to Solution.

We have had an organisation scoped on npm for some time, for the sake of example let's call this org ORGNAME, now with the github package registry, and due to our github org bearing the same name as our npm scope, both scopes are the same. ie: we publish public packages to the ORGNAME scope on npm, private packages to the ORGNAME scope on github

 

It seems that even though we changed to the new proxy setup as explained in the blog, setting up the npmrc file using 

registry=https://npm.pkg.github.com/ORGNAME

the registry will not resolve internally to fall back to the public NPM packages in case the private GitHub package is not available. 

 

wondering if I'm doing something wrong?

4 Replies
Highlighted
Solution
Ground Controller Lvl 1
Message 2 of 5

Re: Github Package Registry scope conflict with proxy

Hi Vincent,

 

I'm not sure if this is any help, but I ran into a similar issue and was able to resolve it by doing this:

 

@ORGNAME:registry=https://npm.pkg.github.com
registry=https://registry.npmjs.org
Highlighted
Copilot Lvl 2
Message 3 of 5

Re: Github Package Registry scope conflict with proxy

that did the trick, thanks

Highlighted
Copilot Lvl 2
Message 4 of 5

Re: Github Package Registry scope conflict with proxy

Seems like it doesn't work anymore. If it works for you, can you pin .npmrc, node version and yarn/npm version?

Thank you!

Highlighted
Copilot Lvl 2
Message 5 of 5

Re: Github Package Registry scope conflict with proxy

This solution is not working for me as of date.