NPM Install from GH Packages: works locally but not in GH action #25587

seriousManual · 2019-11-14T10:44:46Z

seriousManual
Nov 14, 2019

Hello,

I have published a private package to our org’s package repository.

As per the documentation I added an .npmrc file to another project’s root with the following content:

registry=https://npm.pkg.github.com/my-org

In my local ~/.npmrc the sits my Authtoken for npm.pkg.github.com

I installed the published package in my package.json with the following entry in the package.json

"@my-org/my-package": "^1.0.0",

When installing locally this works fine.

When installing via Github Actions the installation fails with the following error:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://npm.pkg.github.com/my-org/@my-org%2fmy-package - npm package "my-package" does not exist under owner "my-org"
npm ERR! 404
npm ERR! 404 '@my-org/my-package@1.0.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)

It seems like “my-org” is used two times in the path to the package?

Why does it work locally but not in Github Actions?

Originally my .npmrc only was like this (no org added to the registry URL):

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

Thas *also* workes fine locally.

It also works for all scoped packages (like @coogle-cloud) in the github Action but did *not* work for unscoped packages:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://npm.pkg.github.com/chai
npm ERR! 404
npm ERR! 404 'chai@4.2.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.