How do I update an NPM module that I published?

Question

I created a NPM module and I published it at version 0.0.1

I made some changes and pushed those to github, and I would like it so that when one uses npm install myModule the new version is used.

How do I tell NPM that there is a version 0.0.2?

possible duplicate of [Do I need to publish to npm every time I update a package available via git?](http://stackoverflow.com/questions/13507763/do-i-need-to-publish-to-npm-every-time-i-update-a-package-available-via-git) — nwinkler, Apr 15 '15 at 12:24

score 136 · Accepted Answer · edited Sep 07 '19 at 12:00

136

Change the version in your package.json or use npm version <new-version>.

After changing the version number in your package.json, you can run npm publish to publish the new version to NPM.

npm install will install the latest version in the NPM repository.

edited Sep 07 '19 at 12:00

aalaap

answered Feb 24 '13 at 20:39

SLaks

3

@AmirRezvani: You still need to change the version & publish. – SLaks Dec 03 '18 at 15:23
1

This took me a surprisingly long time to find an answer to.... – Riza Khan Apr 17 '21 at 23:41

score 34 · Answer 2 · edited Jan 30 '19 at 00:47

34

Increase the version number and then run npm publish yourModule again - as described in the npm docs.

npm install yourModule will then install the latest version from the NPM registry.

I found the last answer a little misleading, sorry.

edited Jan 30 '19 at 00:47

aug

answered Dec 08 '14 at 12:51

how do you increase the version number? – emarel Mar 04 '16 at 00:47
8

`npm version 0.2.0` or `npm version patch` – eljefedelrodeodeljefe Mar 04 '16 at 08:14
@emarel How to increase the version number: https://docs.npmjs.com/getting-started/semantic-versioning – Ilker Cat Jul 21 '17 at 11:50
2

You also need a `npm login` if you're not logged in – icc97 Aug 12 '19 at 14:23

score 10 · Answer 3 · answered Aug 10 '17 at 14:22

10

For me, updating the version in the package.json still resulted in the "You cannot publish over..." error.

The steps to resolve were (based on ops version number):

answered Aug 10 '17 at 14:22

pim

score 9 · Answer 4 · answered Jul 27 '20 at 11:36

If it is an patch release (small changes) use following:
```
 npm version patch
```
It will increment the last part of version number.
If it is a minor release (new features) use following:
```
 npm version minor
```
It will increment the middle part of version number.
If it is a major release (major features or major issue fixes) use following:
```
 npm version major
```
It will increment the first part of version number.

score 6 · Answer 5 · answered Feb 17 '19 at 18:13

To change the version number in package.json, on the command line, in the package root directory, run the following command, replacing <update_type> with one of the semantic versioning release types (patch, major, or minor):

npm version <update_type>
Run npm publish.
Go to your package page (https://npmjs.com/package/) to check that the package version has been updated.

5 Answers5