Do I need to publish to npm every time I update a package available via git?

Say I maintain an incredible crab-season package. I've npm published version 0.1.0 with a package.json containing:

"repository": {
  "type": "git",
  "url": ""

When I add awesome new features, bump the version to 0.2.0, and push to github will the npmjs registry notice my new version or do I need to npm publish each time?


Travis CI can publish to npm when you push a version tag to reduce the overhead of releasing a change. Enable in your .travis.yml with:

  provider: npm
  api_key: "YOUR API KEY"
    - tags: true

Check the travis docs for details. There's also a step-by-step guide in this post.

After publishing a few modules, the answer is yes, you need to npm publish to get new versions on npmjs.

This gives the module author the flexibility to bump their version number as soon as they start work on the next version, or any time before the version is finished.

npm version handily speeds up this flow by detecting a git repository, bumping the version in package.json, committing the change, and tagging the change with the version number.

Need Your Help

How far did DevExpress get with Javascript refactoring?

javascript refactoring devexpress

Over a year ago, I remember watching one of DevExpress evangelists previewing or at least promoting rich Javascript refactoring (beyond just limited intellisense) within the Visual Studio shell, I ...

Filter a Python list by predicate


I would want to do something like: