require.main unexpected behaviour about pm2

[Unitech]

Yes it's normal.

As pm2 wrap code in a "ProcessContainer", the require use the informations of the ProcessContainer.js.

In the process container I've now set require.main.filename to the script you have launched.

It will be available soon

[storkme]

Much obliged, I look forward to trying it out :]

[Unitech]

Pushed on Github, can you try and tell me if everything is okay ? :

$ npm install git://github.com/Unitech/pm2.git -g

[storkme]

Hi, I apologise for replying to this so late.

alex@literally:~/docs/code/node$ npm -g ll pm2

│ /usr/lib
│
└── [email protected]  (git://github.com/Unitech/pm2.git#9b18ca103eb86048fe7f04f8b4143b9059145045)
    The modern CLI process manager for Node apps with native clusterization
    git://github.com/Unitech/pm2.git
    https://github.com/Unitech/pm2
    git://github.com/Unitech/pm2.git

My test file:

console.log(require.main.filename);

using pm2 start test.js I get the following when viewed with pm2 logs:

[test out (l2)] /usr/lib/node_modules/pm2/lib/ProcessContainer.js

If you need any more information let me know -- I'll try and respond more speedily in future.

Cheers.

[Unitech]

Np,

to resolve the script path with require.main.filename, you have to set the option MODIFY_REQUIRE to true https://github.com/Unitech/pm2/blob/master/constants.js#L19

[subeeshcbabu-zz]

Hi,

How do I set the option MODIFY_REQUIRE=true, setting this as a process env (process.env.MODIFY_REQUIRE=true) did not work as expected.