Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Incremented node tag to v0.6.4. Small addition to the article.

  • Loading branch information...
commit 3858e89b371526b3a004a02fbf299d3a230f930f 1 parent 1e894b0
@kishorenc kishorenc authored
Showing with 4 additions and 2 deletions.
  1. +4 −2 articles/managing-module-dependencies.markdown
View
6 articles/managing-module-dependencies.markdown
@@ -1,7 +1,7 @@
Title: Managing module dependencies
Author: Kishore Nallan
Date: Mon Dec 05 2011 16:30:20 GMT
-Node: v0.4.1
+Node: v0.6.4
Following [this discussion](http://groups.google.com/group/nodejs/browse_thread/thread/9aa563f1fe3b3ff5) on the node.js mailing list about managing module dependencies, I thought it's worth sharing some pointers on that here.
@@ -26,9 +26,11 @@ Note that you can either require a specific version of a module, or a minimum ve
If you have development related dependencies (e.g. testing framework) which you do not wish to install in production, specify them using the `devDependencies` property:
"devDependencies": {
- "vows": "0.5.13"
+ "vows": ">= 0.4.x"
}
+On production, using `npm install --production` will ensure that the development dependencies are not installed.
+
## Managing private NPM modules
If you're working on a private module, you can also add `"private": true` to the `package.json` file to prevent yourself from accidentally publishing your module to the NPM registry.
Please sign in to comment.
Something went wrong with that request. Please try again.