On May 28, 2014, at 5:38 PM, Leza Morais Lutonda wrote: > On 28/05/14 10:23, Aria Stewart wrote: >> No. But npm dedup might get you close. It's only theoretically possible if >> your dependencies are transitively compatible -- which is not something many >> people put effort into, since it's not required except to move dependencies >> to the root. What are you actually trying to accomplish? Aria > > Thanks for the answer. > > I try `npm depupe`, but not very happy because the dependencies packages have > different versions of common dependencies. > > I ever wished a npm structure like this: > > node_modules/ > | package1/ > | | version1/ > | | version2/ > | | .... > | | versionN > | package2/ > | | version1/ > | | version2/ > | | .... > | | versionN > ....
*Why* do you wish this? npm is specifically designed to work the way it currently works, because doing so solves some problems. What problem are you trying to solve by circumventing this? -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/6AAA457F-B008-4287-86A9-16F8D6EF6F37%40ryandesign.com. For more options, visit https://groups.google.com/d/optout.
