Menu
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.
268
You can publish a scoped package for free if you are logged in to npm as user 'foo'.
Automating npm tests and publishing When you're done, sign in to your Buddy workspace and do the following: Create a new project, choose GitHub as the provider, and select the forked repository. Add a new pipeline, set the trigger mode to On every push and select Master as the target branch. Add the Node.
To share your code publicly in a user or organization namespace, you can publish public user-scoped or organization-scoped packages to the npm registry.
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
174
You can unpublish a specific version, and then republish it:
npm unpublish [email protected]
And then republish the version.
This works indefinitely if the module is hosted on your own npm repo, but according to this, there's a time-limit (72 hours) in which you can do it if hosted on registry.npmjs.org.
23
According to npm docs this unpublished versions cannot be republished,bump a patch version and publish
Once a package is unpublished, it cannot be republished. If you’ve unpublished a package by mistake, we’d recommend publishing again under a different name, or for unpublished versions, bumping the version number and publishing again.
So:
npm unpublish
npm version patch
npm publish
will do the job.
9
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
