Forcibly republish the package with the same version

Is your feature request related to a problem? Please describe.

Let’s have a situation that I want to keep my package version in sync with other software. I.e.: my-dto:1.2.3, other-software:1.2.3. The problem following: once I have published the package, I can’t easily unpublish it nor forcibly update it. The question is: Is there any way to forcibly republish the package in my private Verdaccio instance with the same version?

Describe the solution you’d like

I want to be able to forcibly update the package which has already been published.

Describe alternatives you’ve considered

or at least be able to unpublish it quickly and then publish it again, so I don’t need to remove entries from the database to erase old package.

Additional context

• I stripped fragile data with XXX.
• My Verdaccio version: 4.1.0

1. The package is already published by in my registry under https://npm.XXX.systems/@my-dto

yarn publish --registry=https://npm.XXX.systems
yarn publish v1.17.3
[1/4] Bumping version...
info Current version: 9.4.0
question New version: 9.4.0
[2/4] Logging in...
[3/4] Publishing...
error Couldn't publish package: "https://npm.XXX.systems/@my%2fdto: this package is already present"
info Visit https://yarnpkg.com/en/docs/cli/publish for documentation about this command.

[Qix-]

Please remember that people use Verdaccio for development, too. Trying to add a feature to @storybookjs is currently a massive headache - I have spent the last two hours trying to figure out how to get Verdaccio to play nice.

I’m developing locally. I don’t care about npm’s silly package publishing policies. If I write --force, I mean it. Let me publish over versions without having to unpublish.

If you’re really scared about this, at least let me specify it in the Verdaccio configuration that force publishes are OK.

[DanielRuf]

A dev mode sounds good.