module.parent.filename is cached.

[nazomikan]

When a file is called twice, module.parent is cached.
Is this correct behavior?

/home/xxx/yyy/module_parent/
├── a.js
└── up
    ├── b.js
    └── up
        └── c.js

a.js

var b, c = require('./up/up/c');
c.dump();
b = require('./up/b')

b.js

var c = require('./up/c');
c.dump();

c.js

exports.dump = function () {
  console.log(module.parent.filename);
}

console

/home/xxx/yyy/module_parent/a.js
/home/xxx/yyy/module_parent/a.js

[bnoordhuis]

When a file is called twice, module.parent is cached.
Is this correct behavior?

Yes, it is. The module gets evaluated only once so its parent is the module that first require()s it.

[nazomikan]

I see... thank you!
Is there a way to access to the caller in any other way?

[isaacs]

Is there a way to access to the caller in any other way?

No. Please find another way around. Export a function, and call it with the relevant data if you care about this.

[isaacs]

eg:

// a.js
module.exports = function(caller) {
  doSomething(caller)
};

// b.js
var a = require('./a.js');
a(__filename);

[nazomikan]

All right. thx!

Initially, I thought it's possible if change the cacheModule.parent in Module._load , but on second thought, i understood this was bad way.
I had forgotten that the bad impact would be out on the side that is already loaded.
To clone the cacheModule also is a cost of its own way, and I decide to give up:)

As of advice I have received from you, so i decide to give the file path.
Thank you carefully!!:)

[jakswa]

I ran into this unexpected behavior as well. I wish the property was called module.originalParent or something. Or maybe just have the docs explicitly state that it isn't "The module that required this one" but is actually, "the first module that required this one" or something.

[jorrit]

That last change @jakswa mentioned would be very welcome.