Sometimes I don't want to npm link in case I forget to unlink later. Alternatives include:
npm install /path/to/other/module (every time you update /path/to/other/module) or just edit node_modules/themodule/* directly until satisfied, then copy the changed files into your actual source repo. it's hacky but effective. On Saturday, December 7, 2013 1:48:37 PM UTC-5, Dave Horton wrote: > > I'm developing two related modules concurrently -- module A depends on > module B. Neither is anywhere near a state where I want to put them into > npm yet, so I can't simply have module A have a dependency on B in its > package.json and leave it at that. I'm thinking what I will do is have the > projects in separate folders (separate git repos) on my laptop, and then > just make a symbolic link under A/node_modules to where B is, so I can > modify B real-time and then test it as I run tests/examples on A. > > But I'm thinking this must be common, and whether smarter people than me > have figured out a better approach for this... > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
