Releasing & maintaining modules for nodejs
So I’ve just released my first module for nodejs.
Things that I did:
- picked a SEO-oriented name
- posted the code on github
- added the module to the list of modules
- published the module via
- Do I need to do more than that, to make sure who needs it will get to my module?
- How do I push updates with npm? I tried doing
npm publishagain, but it says I need to unpublish first, or change versions or do crazy things.
One Solution collect form web for “Releasing & maintaining modules for nodejs”
Do I need to do more than that, to make sure who needs it will get to my module?
You’ve covered your bases as far as the basics are concerned. You may consider writing in to blog sites like DailyJS or post to some mailing lists to get the word-of-mouth out, but having your code on GitHub and your package on NPM is a solid start.
How do I push updates with npm?
Once you’ve published a specific version of your module, you should not push a change to that same version–this ensures that people that expect a certain version of your module to behave a certain way can ensure that it does so. If you need to update your module, you should bump the version number in your
package.json file and publish that.
Be sure to stick to semantic versioning when picking version numbers, so version matchers like
~3.0.5 work. See http://npmjs.org/doc/json.html#version for more details.