Is there a workaround for `npm publish -f`

node.js npm semantic-versioning
Alexej Magura picture Alexej Magura · Jan 10, 2015 · Viewed 20.4k times · Source

Now that npm publish -f is deprecated, is there a workaround or a package that makes it possible to overwrite a target version after it's been published?

I know about semver; I still want npm publish -f.

Answer

c0b0 picture c0b0 · Jul 31, 2016

someone said this on npm's github issue:

@nmrony You cannot overwrite previously-published packages anymore (since February 2014, if I recall correctly).

https://github.com/npm/npm/issues/8305#issuecomment-236412989

Related questions

What's the difference between tilde(~) and caret(^) in package.json?

After I upgraded to latest stable node and npm, I tried npm install moment --save. It saves the entry in the package.json with the caret ^ prefix. Previously, it was a tilde ~ prefix. Why are these changes made in npm? …

Read More
What is the convention for versioning npm packages prior to 1.0.0?

I was reading up on versioning with npm, and apparently it provides a nice convenient command for bumping your package versions. npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease] prerelease Lets say your package starts at …

Read More
npm install using pre-release versions

i want to use pre-release versions in my package.json to get some dependencies in the latest version (containing als pre-releases) but for some reasons it doesn't work in my case. The pre-releases are fully ignored. As an example lets …

Read More