-------- Forwarded message ------- From: [email protected] To: "Pirate Praveen" <[email protected]> Sent: November 2, 2016 3:51 PM Subject: Re: [Pkg-javascript-devel] How debian manages npm module version conflicts ? November 2, 2016 2:21 PM, "Pirate Praveen" <[email protected]> wrote:
> On Wednesday 02 November 2016 03:50 PM, [email protected] wrote: > >> Does debian allow installation of multiple version of same npm module >> via package manager ?. >> >> If not how will debian manage version conflicts like module a requires >> module c@1 and module b requires c@2 ? > > We'll update module a to use c@2. As a last resort we can add version > number to the package like node-c1, node-c2 or embed c@1 in a or embed > c@2 in b, but that is really a last resort. > > I think the question was triggered by this > https://github.com/jonschlinkert/global-modules/issues/5 > > Is there a way we can distinguish if the module is accessed via npm or > native debian nodejs? > > The command name always seem to be nodejs and node is a symlink to nodejs. process.env._ gives it, but global-modules' description says that it returns "The directory used by npm for globally installed npm modules." and its always '/usr/lib/node_modules' > -- > Pkg-javascript-devel mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
