.npmrc content doesn't always pass legacyRegex validation on Windows

[exaucae]

The .npmrc at the root of my project does not pass the legacyRegex validation although it should.

>npx google-artifactregistry-auth --credential-config=./.npmrc
Retrieving application default credentials...
Success!
${home}\AppData\Local\npm-cache\_npx\64aef35f3ba01c7c\node_modules\google-artifactregistry-auth\src\update.js:131
    throw new Error(
          ^

Error: Artifact Registry config not found in ${path}\.npmrc
Run `gcloud beta artifacts print-settings npm`.
    at updateConfigFile (${home}\AppData\Local\npm-cache\_npx\64aef35f3ba01c7c\node_modules\google-artifactregistry-auth\src\update.js:131:11)

Is there anything I am missing?

Find relevant config below:
.npmrc

@scope:registry=https://my-registry
//a-region-npm.pkg.dev/project/repo/:_password="foo"
//a-region-npm.pkg.dev/project/repo/:username=oauth2accesstoken
//a-region-npm.pkg.dev/project/repo/:email=radom@email.com
//a-region-npm.pkg.dev/project/repo/:always-auth=true

OS Name:                   Microsoft Windows 10 Professionnel
OS Version:                10.0.19043 N/A Build 19043
NPM                           7.20.3
NODE                         v16.6.2

Google Cloud SDK 368.0.0
beta 2022.01.07
bq 2.0.72
core 2022.01.07
gsutil 5.6

One key point is that I have several projects wherein some have the setup correct, while others just fail before working later on with the same .npmrc.

I am updating the issue title based on that.

[yihanzhen]

Hi @exaucae

I can't repro the issue with the sample input you have above, in which case the plugin found the match and updated the token successfully.

You changed the title to "it doesn't always work", do you have a sample input where the plugin fails to update consistently, or is the failure intermittent even with the same input?

[exaucae]

It's intermitent with the same input @yihanzhen.

[exaucae]

Update
Removing the @scope allows .npmrc to be updated:

- @scope:registry=https://my-registry
+ registry=https://my-registry
//a-region-npm.pkg.dev/project/repo/:_password="foo"
//a-region-npm.pkg.dev/project/repo/:username=oauth2accesstoken
//a-region-npm.pkg.dev/project/repo/:email=radom@email.com
//a-region-npm.pkg.dev/project/repo/:always-auth=true

But then no other public package can be downloaded: the package manager now points to the private registry.

So the hack for now is to:

• first remove the scope
• then run npx google-artifactregistry-auth
• finally reset the scope

Would appreciate any insight about this.