On May 28, 02014, at 18:38, Leza Morais Lutonda <[email protected]> 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 > .... > > And maybe node resolve the path for `require` on starting the application > reading de package.json. > > Anybody else wished this? Sometimes, but what does this get you? What are the trade-offs? What are you actually trying to accomplish?
signature.asc
Description: Message signed with OpenPGP using GPGMail
