How to fix 404 error when installing npm package from GCP artifact registry with yarn?

Question

I'm having an issue with installing an NPM package from GCP.

I was able to upload the package to the artifact registry of GCP by doing the following steps:

1. Login to my google account (gcloud auth application-default login)

2. Run

   gcloud artifacts print-settings npm \ --project=[my-project]\ --repository=[my-repo] \ --location=us-east1 \ --scope=@[my-scope]

3. Pasting the output of the previous step in the .npmrc file located in the root of the project.

4. Refreshing the access token to GCP (npx google-artifactregistry-auth ./.npmrc)

5. Run yarn publish

My .npmrc file looks like this:

@[my-scope]:registry=https://us-east1-npm.pkg.dev/[my-project]/[my-repo]/
//us-east1-npm.pkg.dev/[my-project]/[my-repo]/:_authToken="[auth-token]"
//us-east1-npm.pkg.dev/[my-project]/[my-repo]/:always-auth=true

However, when I try to install the package on another project by:

1. Executing steps 1-4 mentioned above
2. Run yarn add @[my-scope]/[my-package]

I get an 404 error. Looks like yarn is looking for the package in the default registry:

error An unexpected error occurred: "https://registry.yarnpkg.com/@[my-scope]/@[my-pacakge]/-/@[my-scope]/[my-package]-0.0.1.tgz: Request failed \"404 Not Found\"".

I simply followed the steps mentioned in the installation instructions in GCP but somehow it's not working.

I encountered a similar issue in this post: Can't install a scoped package I published to a npm registry in GCP but this not the exact error I get.

I would appreciate any help regarding this issue.

Thanks in advance!

Answer 1

I just had this problem for a couple of days and the solution is simple, DO NOT USE YARN when publishing. That's it.

I don't know which part of yarn causes this but basically it ignores .npmrc resulting in the tarball to point to the wrong repository, you can check it if you run yarn info. So when publishing to GCP artifact registry one should use npm publish instead.