[Pkg-javascript-devel] How debian manages npm module version conflicts ?

[Pirate Praveen]

On Wednesday 02 November 2016 03:50 PM, shanavas at disroot.org 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 at 1 and module b requires c at 2 ?

We'll update module a to use c at 2. As a last resort we can add version
number to the package like node-c1, node-c2 or embed c at 1 in a or embed
c at 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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/attachments/20161102/74cc8053/attachment.sig>