Cached version not refreshed when uplink's version updated

Cached version not refreshed when uplink’s version updated

To Reproduce

• publish to uplink
• query package info at local
• deprecate uplink’s package version
• local version should also be deprecated but not

This behavior seems like by design. (https://github.com/verdaccio/verdaccio/blob/master/src/lib/metadata-utils.ts#L22)

What’s the purpose of this and how should we refresh the local cache?

[Amorites]

@Amorites what do you mean with deprecate uplink's package version? Deprecate on npmjs for instance? Just want to be sure I understood correctly.

Yes, for example, the package name is mylib.

• npm publish --registry https://registry.npmjs.org/
• npm info mylib --registry http://localhost:4873
• npm deprecate mylib@1.0.0 deprecate-it --registry https://registry.npmjs.org/
• The results of npm info mylib --registry http://localhost:4873 and npm info mylib --registry https://registry.npmjs.org/ are different.

[zhangschunfeng]

root@a3cb7a1ace6f:/# npm config list ; cli configs metrics-registry = “http://172.48.52.81:4873/” scope = “” user-agent = “npm/6.14.12 node/v12.22.1 linux x64”

; userconfig /root/.npmrc registry = “http://172.48.52.81:4873/”

; node bin location = /usr/bin/node ; cwd = / ; HOME = /root ; “npm config ls -l” to show all defaults.

root@a3cb7a1ace6f:/# npn install xlsx@^0.17.1 bash: npn: command not found root@a3cb7a1ace6f:/# npm install xlsx@^0.17.1 npm ERR! code ETARGET npm ERR! notarget No matching version found for xlsx@^0.17.1. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn’t exist.

npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-08-19T08_57_40_572Z-debug.log root@a3cb7a1ace6f:/# exit

uplink’s version updated xlsx@^0.17.1. is exist ,but i cant got

How to solve or circumvent