npm WARN registry No auth for URI, but auth present for scoped registry.

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

we have NodeJS 12 base image and now we upgraded to Nodejs16. NPM version used is 8.11.0

When we tried to build the docker image through Azure CI/CD getting the error "npm WARN registry No auth for URI, but auth present for scoped registry"

"https://private.registry.com/[project]/_packaging/[scope]-framework@Local/npm/registry/@[scope]/auth-lib/-/auth-lib-0.1.1-preview.1026678.tgz" -- this seems not a valid one.

what exactly this tgz file refers to? And from where it's been picked up. Request to help me on this

.npmrc file for reference
@[scope]:registry=https://private.registry.com/[project]/_packaging/[scope]-framework%40Local/npm/registry/
always-auth=true

npm WARN registry No auth for URI, but auth present for scoped registry.
npm WARN registry
npm WARN registry URI: https://private.registry.com/[project]/_packaging/[scope]-framework@Local/npm/registry/@[scope]/auth-lib/-/auth-lib-0.1.1-preview.1026678.tgz
npm WARN registry Scoped Registry Key: //private.registry.com/_packaging/[scope]-framework%40Local/npm/
npm WARN registry
npm WARN registry More info here: https://github.com/npm/cli/wiki/No-auth-for-URI,-but-auth-present-for-scoped-registry
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.

Expected Behavior

Expected behavior is Azure docker task run with node.js base image without any issues. And azure application service should show node version 16 when we verified it from Kudu.

But the node version is showing 14 when we use node -v command to check node version status from Azure app service.

Steps To Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...

Environment

• npm: npm 8.11.0
• Node.js: 16-slim
• OS Name: Azure Agent Linux
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

Start with the npm 8.11.0 warning, the provided .npmrc scoped-registry settings, and the reported Azure registry URI. Compare how the Node 16-slim Docker environment and Azure App Service report their Node versions. Done means the source of the package URI and authentication warning is established, with the expected Node version behavior clarified.