Npm private server releases the package, but overwrites the cache that was previously released to npm

A set of components mUI, is first released to npm with version v2.0.0.
later builds a set of npm private servers, and then publishes mUI to private servers, and the version is changed to v1.0.0. After
then switches to private servers to install mUI, on, npm install, the mUI on private servers becomes the v2.0.0
version on npm.
that is, all the dependent packages used are cached on the private server, and the mUI is also cached from the npm to overwrite my private server.
how should I configure so that the npm private server only keeps my own components, and the rest go to npm to find

May.25,2021

  1. is the fixed version number used when using private server installation? If you specify version 1.0.0, it should be pulled down from the private server.
  2. at present, there should be two versions of mUI, in hosted warehouse v1.0.0 and proxy warehouse v2.0.0. Instead of directly covering it.
  3. Private server mechanism means that packages that are not available on private servers will be downloaded to private servers at the address specified by proxy, so as to ensure the success of installation. If you really only want to download the package on private server, if you don't have it, you can report an error. You can try setting proxy to yourself (I haven't tried it?)
Menu