NPM Authentication and the Cache

[JamesPoli]

Hello,
Our company uses an NPM Registry in Artifactory to store packages. We are switching from a version of an Artifactory server that allows anonymous access to one that requires an identity token (authentication) for each user's home ".npmrc" file.
While switching from the Artifactory server that allows anonymous access to the one that requires an identity token, I noticed the package in the cache is reused, with no authentication to the new registry. Is this working as designed? Should we move to a newer version of NPM? Our company is currently using 3.10.10.
Thanks in advance for any insight.
Regards, Jim

[Aman3899]

Okay, Jim's NPM's caching old packages even after switching to an Artifactory server that requires authentication. He's on NPM 3.10.10.

Answer: Yes, this is likely due to the old NPM version. Upgrade NPM! Then, npm cache clean --force, double-check .npmrc for correct authentication, and test package installation. Newer NPM handles authentication much better.