Should it be module.parent.parent?

[phillee]

Currently, parent-require calls require in module.parent, which is the calling module.

However since it's "parent-require" I think it should be looking in the module's parent, which is module.parent.parent

[phillee]

Forked it here: https://github.com/Healtho/node-parent-require. It's working well for me and solves some nasty dev-time peerDependency issues, let me know what you think.

[jaredhanson]

That would be grandparent, not parent. Can you provide some details on the situation you are encountering and describe the problem in more detail?

Sent from my iPhone

On Sep 6, 2014, at 1:48 AM, Philip Lee notifications@github.com wrote:

Currently, parent-require calls require in module.parent, which is the calling module.

However since it's "parent-require" I think it should be looking in the module's parent, which is module.parent.parent

—
Reply to this email directly or view it on GitHub.

[phillee]

Using the Readme example:

• my-app
  • requires mongoose-schemas-users
    • requires parent-require < my-app is grandparent here

I believe the goal is to have my-app (the parent) require mongoose. With the above setup, from parent-require, module.parent is mongoose-schema-users and module.parent.parent is my-app.