The situation would be:

I develop 2 projects in my Node.js development environment, P1 and P2.

P1 required the development of two simple modules, mod1 and mod2, which are stored in P1/lib. Each one of this modules resolves find their external dependencies in P1/node_modules. Necessary dependencies for P1 have been installed in this folder via npm.

Now image we want to reuse mod1 in the other proyect P2, here's were my doubts come up. I could...

  • Just copy mod1 to P2/lib. Replication, so I don't even consider this option.

  • From P2, reference mod1 from P1: require($PROJECTS_DIR + '/P1/lib/mod1'). Not a good option, this way P2 would depend on P1.

  • Put mod1 into a higher level directory or using NODE_PATH, so that P1 and P2 can resolve it by just doint require('mod1'). However, when deploying, I should also deploy this higher level directory which seems a bit dirty.

  • I would like to treat mod1 as a npm module, so it can be easily installed in any project or environment, However, in this particular case, I can't publish the module to npm cause is too project-specific. I could create a private npm repository and put mod1 inside. The gist of this would be to set it up in order to be accessed also from the production envirnoment. Is it worth it?

  • What about putting it all together in node_modules? (external depencencies and my own libraries). That would be great since modules can be just required like `require('module'). But it also seems quite dirty.

  • Not sure how npm link would work when deploying. It creates a symbolic link, which is not followed when commiting code via Git or SVN. If I run npm install in production, will it also install the linked module?

None of the above quite satisfies me. I don't know if one of these is suitable, or you guys have other suggestions, but, are there any preferred ways to structure own private libraries so that they can be easily reused in other projects?

1 Answer 1


Use npm link. It allows you to have a module wherever you want, and you can then "link" it in your project (a symbolic link will be created in your node_modules/ folder), thus you can use it with require('mod1'). Your module has to be npm-compatible.

More information here: https://docs.npmjs.com/cli/link

About your private concerns, npm thought about this and provides the private option. See here: https://docs.npmjs.com/misc/registry (Go to : "I don't want my package published in the official registry. It's private.")

For each module dependency, you can simply define them in the package.json.

  • Thanks Florian, when I commit changes via svn or git, I don't get symlinks followed. Does it mean that I would have to use npm link also in the production environment? Or is it implicit in npm install .Any ways to specify it in package.json ?
    – jaime
    Jan 23, 2013 at 12:17
  • @jaime git and svn follow symlinks. Jan 23, 2013 at 12:43
  • In production environments, I'd run a script to package the modules in the node_modules/ folder though. Jan 23, 2013 at 12:44
  • @jaime You only need to use npm link when developing.
    – Daniel
    Jan 23, 2013 at 16:39
  • docs.npmjs.com/… - 404's. But really the best way to keep things private is to not put them up on the internet. It sounds like link is the best option as well ... except npmjs.org/doc/link.html 404's as well. Got to love link rot.
    – Pat
    Jan 12, 2015 at 19:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.