Always resolves to module root

[inxilpro]

Always resolves to module root

[inxilpro]

Hmm… I can see how symlinked files could cause issues, assuming that the actual path to the module contains node_modules in it. I'm honestly not sure the best way to approach this problem. In this scenario you're probably better off just using the alternate method:

path.dirname(require.main.filename);

This will work as long as you're not using something like pm2 to run your app.

I'll dig into this further… not sure if there's going to be a universal solution to this particular setup.

[newz2000]

Thanks, in the mean time with the app I'm building I have a configuration object where I can pass the path through, which I'll do. I found your project based on the Stack Overflow discussion. If you ever do get any clever ideas I'd love to hear more. If I come up with something better I'll share it here too.

[inxilpro]

I'm going to close this for now. I don't think there is a solution to this particular use-case.

[enuggetry]

I think I hit this problem.
mymodule uses app-root-path. it had always work installing the module using the traditional npm install method. But, when I used npm link, it failed.
I am copying something into the app root directory. As an npm link module, app-root-path returns /home/me/mymodule, not /home/me/myapp. using npm link, /home/me/mymodule is symlinked into /home/me/myapp/node_modules/mymodule.