Add support for Artifact Registry in yarn

[yutaroyoshikawa]

I have a web project that uses yarn v1 for package management hosted on Google App Engine. Newly, I am trying to use private npm packages managed by Artifact Registry in my project. I believe that buildpacks recognizes the .npmrc when building App Engine and automatically generates an access token if the package manager is npm, but yarn does not support automatic generation of this access token, so I would like you to consider supporting this.

[AkselAllas]

+1 for this. Ran into the same problem. ❤️

[jama22]

Makes sense. For additional context, it sounds like a request to extend the capabilities of this feature we introduced in App Engine / Cloud Functions (https://cloud.google.com/appengine/docs/standard/nodejs/specifying-dependencies#private_dependencies_with_artifact_registry) that allows users to access their packages hosted in Artifact Registry without performing additional configuration.

I think yarn would be a good next package to pick up to support Node.js workloads

[savarex]

+1 for this. Ran into the same problem.

[kritkasahni-google]

Enabled AR support for yarn1 -> https://github.com/GoogleCloudPlatform/buildpacks/commit/92cbbdebc4f810d757e2dc44fa9599fca9a7936c

[kritkasahni-google]

Enabled AR support for yarn2 -> https://github.com/GoogleCloudPlatform/buildpacks/commit/e924f3bfa5ed17e0d755b6df24568e5f6f57eb34

[jama22]

For future reference, docs have also been updated on GCP Buildpacks Node.js page