I'm kind of lost here!
I'm using a module which has another module nested in its' node_modules. I.E.
my_project
node_modules
widely_used_module
parent_dependency
node_modules
widely_used_module
I have some fixes in my "own" widely_used_module (it could be just a minor version from the original distributor, but to be completely honest, in this case its' my fork on Github containing some critical fixes).
When I manually remove node_modules/parent_dependency/node_modules
, parent_dependency starts to reference to my "widely used module" instead of its' own. But this of course gets overriden once I hit npm install again.
- Can I somehow prevent a package to install its' own modules, or can I force a package to reference the root node_modules and ignore its' own?
- Is that even the right approach to fixing such issues? I don't want to fork parent_dependency as well...
Thank you