Stubbing peer dependencies about proxyquire HOT 3 CLOSED

If you are overriding a dependency of a module in your project, by definition that is not a peer dependency.

If you are overriding a transitive dependency that requires the @global option.

If that's not the issue we'll need a fully reproducible example.

from proxyquire.

If you are overriding a dependency of a module in your project, by definition that is not a peer dependency.

What is then a peer dependency by definition?

If you are overriding a transitive dependency that requires the @global option.

It's not transitive.

If that's not the issue we'll need a fully reproducible example.

You can reproduce the above with any setup that has npmmodule (placeholder; take any module you like) it in peerDependencies in package.json and not being installed, thus not being present in node_modules.

Why you just closed it after replying with a non-answer? This is not some kind of please give me full instructions kind-of question. I read the docs and I tried the things but I just don't see, why stubbing a module, that is simply not present, is not possible. Maybe I just don't understand the require system enough but at least you could give me a hint here.

from proxyquire.

A peer dependency is a dependency of another npm package you depend on. By definition, a module that you require relatively cannot directly require a peer dependency.

Given the above, this seems like a support/usage issue. If you can demonstrate a bug through runnable code I will of course reopen. Argumentativeness will not be tolerated though.

from proxyquire.