the way how node module loader resolves modules allows it to place C only once in the hierarchy of dependencies. B still has access to C. http://nodejs.org/api/modules.html#modules_all_together describes, how the resolver works.
Am Freitag, 12. Juli 2013 04:53:10 UTC+2 schrieb Maxim Yefremov: > > I got module *A* that depending on module *B* by git dependency and > module *B* depending on module *C*. At the same time module *A* depends > on module *C* by git dependency. When I do *npm install *for *A* it > install *B* and *C* in *node_modules *but in * > A/node_modules/B/node_modules* I do not see C folder as expected. If I > remove dependency *C* from *A* it install *B* with dependency* C* well. > But I want *A* to depend on *C *too. -- -- 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.
