Add an Azure NPM registry

[agocke]

No description provided.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[agocke]

/azp run runtime-extra-platforms,runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[agocke]

Looks like the npm stuff is failing auth. @adiaaida Did you run into this by any chance? Any suggestions?

[mmitche]

@agocke You'll need to npm install these locally on your machine to ingest the required packages.

[agocke]

@mmitche The CI is failing with

npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login

Is that the same problem or different?

[mmitche]

@mmitche The CI is failing with

npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login

Is that the same problem or different?

@adiaaida has more experience with this, but I think it's the same. The package feed is anonymously accessible, but the packages required may not be available, requiring authentication to ingest.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	agocke
Assignees:	agocke
Labels:	area-Infrastructure
Milestone:	-

[michellemcdaniel]

Did you run

vsts-npm-auth -config .npmrc

First? You may also have to go through these instructions first:

To use npm packages, get npm (which comes with Node.js) and the vsts-npm-auth helper.
Step 1
[Download Node.js and npm](https://go.microsoft.com/fwlink/?linkid=2103882)

Step 2
Run this command

npm install -g vsts-npm-auth --registry https://registry.npmjs.com --always-auth false

(locally)

[agocke]

/azp run dotnet-linker-tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[agocke]

I've tried running vsts-npm-auth -config .npmrc and it seemed to work but after re-running the tests they fail in the same way.

[mmitche]

I've tried running vsts-npm-auth -config .npmrc and it seemed to work but after re-running the tests they fail in the same way.

Please ensure your npm cache is cleaned locally so that the ingestion happens (rather than picking up packages locally)

[michellemcdaniel]

Run to make sure you're getting everything ingested.

npm cache clean –force
git clean -fxd

[agocke]

OK, figured it out, I was running this in Linux and that apparently doesn't work.

[michellemcdaniel]

Oh yeah, there are different instructions for Linux. If you go to https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet-public-npm/connect/npm and click the "Other" tab in project setup, it will tell you how to auth on Linux/Mac

[agocke]

Well, looks like it works locally, but still hasn't fixed CI.

[michellemcdaniel]

I would reach out to the folks who work on wasm to see if maybe something about the .npmrc file and how they run npm ci/install are interacting poorly.

[michellemcdaniel]

Oh, the log says npm audit isn't supported and they're using npm audit:

npm ERR! audit Your configured registry (https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public-npm/npm/registry/) does not support audit requests.

[agocke]

@steveisok Any idea who could look at this npm audit issue?

[steveisok]

@steveisok Any idea who could look at this npm audit issue?

@lewing @radical

[agocke]

ping @lewing @radical

[radical]

 npm info it worked if it ends with ok
  npm verb cli [
  npm verb cli   '/usr/local/emscripten/emsdk/node/14.18.2_64bit/bin/node',
  npm verb cli   '/usr/local/emscripten/emsdk/node/14.18.2_64bit/bin/npm',
  npm verb cli   'audit',
  npm verb cli   '--verbose'
  npm verb cli ]
  npm info using npm@6.14.15
  npm info using node@v14.18.2
  npm verb npm-session b8f1af247e4fb9ba
  npm http fetch POST 404 https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public-npm/npm/registry/-/npm/v1/security/audits 158ms
  npm verb stack Error: Your configured registry (https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public-npm/npm/registry/) does not support audit requests.
  npm verb stack     at /usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/lib/audit.js:204:18
  npm verb stack     at tryCatcher (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
  npm verb stack     at Promise._settlePromiseFromHandler (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:517:31)
  npm verb stack     at Promise._settlePromise (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:574:18)
  npm verb stack     at Promise._settlePromise0 (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:619:10)
  npm verb stack     at Promise._settlePromises (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:695:18)
  npm verb stack     at _drainQueueStep (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:138:12)
  npm verb stack     at _drainQueue (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:131:9)
  npm verb stack     at Async._drainQueues (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:147:5)
  npm verb stack     at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/emscripten/emsdk/node/14.18.2_64bit/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
  npm verb stack     at processImmediate (internal/timers.js:464:21)
  npm verb cwd /__w/1/s/src/mono/wasm/runtime
  npm verb Linux 5.4.0-1080-azure
  npm verb argv "/usr/local/emscripten/emsdk/node/14.18.2_64bit/bin/node" "/usr/local/emscripten/emsdk/node/14.18.2_64bit/bin/npm" "audit" "--verbose"
  npm verb node v14.18.2
  npm verb npm  v6.14.15
  npm ERR! code ENOAUDIT
  npm ERR! audit Your configured registry (https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public-npm/npm/registry/) does not support audit requests.
  npm verb exit [ 1, true ]

@lewing @pavelsavara @maraf Any idea what could be done here? Since the exception also shows the same error npm verb stack Error: Your configured registry (https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public-npm/npm/registry/) does not support audit requests., does it mean that the registry really doesn't support audit?

[maraf]

does it mean that the registry really doesn't support audit?

It probably doesn't https://docs.microsoft.com/en-us/azure/devops/artifacts/npm/npm-audit?view=azure-devops&tabs=yaml

Azure DevOps does not support npm audit, if you try to run the default npm audit command from your pipeline, the task will fail with the following message: Unexpected end of JSON input while parsing....
As a workaround, you can run npm audit with the registry argument --registry=https://registry.npmjs.org/. This will route the npm audit command directly to the public registry.