CI Build error restoring npm packages

[noahfalk]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1318883&view=logs&j=b21266ef-9242-50d9-7178-994c59fc8dbe
Build error leg or test failing: Build / browser-wasm windows Release CoreCLR / Build product
Pull request: #124410

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "FAILED: [code=1] D:/a/_work/1/s/src/native/node_modules/.package-lock.json",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1318883
Error message validated: [FAILED: [code=1] D:/a/_work/1/s/src/native/node_modules/.package-lock.json]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/4/2026 1:58:04 AM UTC

Report

Build	Definition	Step Name	Console log	Pull Request
1318883	dotnet/runtime	Build product	Log	#124410

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	1	1

[dotnet-policy-service]

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

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.

[radekdoulik]

This looks like network problem during the build. Happened just once so far.

  [21/843] Running 'npm ci' to install npm packages
  FAILED: [code=1] D:/a/_work/1/s/src/native/node_modules/.package-lock.json 
  C:\Windows\system32\cmd.exe /C "cd /D D:\a\_work\1\s\src\native && npm ci"
  npm ERR! code ECONNRESET
  npm ERR! network aborted
  npm ERR! network This is a problem related to network connectivity.
  npm ERR! network In most cases you are behind a proxy or have bad network settings.
  npm ERR! network 
  npm ERR! network If you are behind a proxy, please make sure that the
  npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

[akoeplinger]

Yeah this looks like a temporary issue. Given it was hit just once in the last month I don't think it makes sense to track it as a Known Build Error.