There is the npm link command that does just this. I don't know if it works on windows though since it uses symlinks. If it doesn't work, then yes nesting works just fine. Git is fairly good at ignoring nested repos automatically.
On Mon, Feb 13, 2012 at 1:57 PM, Phoscur <phos...@pheelgood.net> wrote: > Hi, > After reading this: > http://www.debuggable.com/posts/how-to-fork-patch-npm-modules:4e2eb9f3-e584-44be-b1a9-3db7cbdd56cb > I see there is a nice way to replace broken modules with your own > patched ones. But this always involves git push and npm update commands > when you change something. Isn't there an easier way to do this locally? > Like linking the module folder in node_modules to my local checkout of > the my forked module? > How do I accomplish this on windows? > Would it be better to just nest the projects? > > regards, > Ph > > -- > 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 nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
