Package lock retains localhost after using verdaccio

[mallowigi]

I am having a bit of troubles with Verdaccio.

I discovered this tool to help me work on publishing libraries. Before, I was constantly using the global npm registry, and for every change I had to publish a patch, which resulted in a lot of versions that are useless. So when I discovered verdaccio, this looked like the tool I've been waiting all along.

So I started publishing the fixes to the local verdaccio storage, until I was happy with the state of the libs and decided to publish them to the global npm.

But after I did that I found out that even after changing the registry back to registry.npm.org, the package-lock still retained instances of localhost, and users using my libraries reported not being able to build the project.

And nothing was said in the documentation about this!!!

Obviously I tried fixing that by doing npm install on the repositories. But alas, it didnt remove the instances. Then I tried removing the package-lock and reinstall. No success.

Finally I got it to work by removing node_modules and doing npm cache clean --force.

This is very tedious, there's no way I can recommend people to use this tool if they have to remember to do all these steps before publishing...

Is there a better way to fix that problem?