I have some scoped public packages on npm registry as using scopes seems to be a good practice in general. Of course I have the same username on npm registry and GitHub and both registries require that the scope I can publish to is my username - which all makes sense.
I have published a private package to GPR call it `@activescott/my-private-package`. I can install that package successfully using the `.npmrc` as follows
registry=https://npm.pkg.github.com/activescott //npm.pkg.github.com/:_authToken=MY_PERSONAL_ACCESS_TOKEN always-auth=true
and the following install command:
$ npm install @firstname.lastname@example.org
The issue comes when I try to install a public package with this command:
npm add @activescott/eslint-config
I get the following error:
npm ERR! code E404 npm ERR! 404 Not Found - GET https://npm.pkg.github.com/activescott/@activescott%2feslint-config - npm package "eslint-config" does not exist under owner "activescott" ...
How can I pull some packages from the same scope that are private on GPR and public on npm registry?
@activescott did you figured out the solution for this situation. Me too running into the same problem.