pkozlowski-opensource / batmobile.js Goto Github PK

create a new dependency foo with a transitive dependency bar the also add bar to the main package.json but use slightly different version patterns for both with some version overlap.

ideally dedupe should pick the latest version within the overlapping range for both dependencies

Similar setup to #2 but change one of the version ranges to not overlap with the other.

Ideally dedupe should complain. I'm not sure if that's going to happen though
we could change dedupe to do that though in our fork.

what happens when we have a transitive dependency (M2) that is not in the main package.json.

That package will end up in node_modules folder of the component that depends on it (M1) and not in the main node_modules folder. That's ok for now.

But the question is will importing M2 module from module M1 still work? or will we need to adjust paths somewhere because now the modules come from different folders on the file system?