why-is-node-running: Cannot find module 'internal/linkedlist'

Heyo, I just wanted to play around with this to see how it works. Apparently I don’t get it to work. 😦

I’ve got a simple index.js.

var log = require('why-is-node-running') // should be your first require

log();

And why-is-node-running is available installed in my node_modules.

That’s what I got:

stefan @ stefan-mac: ~/Downloads/test
> node --version
v5.0.0

stefan @ stefan-mac: ~/Downloads/test
> node ./index.js
module.js:339
    throw err;
    ^

Error: Cannot find module 'internal/linkedlist'
    at Function.Module._resolveFilename (module.js:337:15)
    at Function.Module._load (module.js:287:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at timers.js:4:11
    at NativeModule.compile (/Users/stefan/Downloads/test/node_modules/why-is-node-running/core.js:108:3)
    at Function.NativeModule.require (/Users/stefan/Downloads/test/node_modules/why-is-node-running/core.js:52:16)
    at Object.globalTimeouts (/Users/stefan/Downloads/test/node_modules/why-is-node-running/core.js:14:31)
    at Object.<anonymous> (/Users/stefan/Downloads/test/node_modules/why-is-node-running/index.js:50:6)
    at Module._compile (module.js:425:26)
FAIL: 1

Thanks.

Any hints are more than welcome. :bowtie:

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 38
Comments: 21 (3 by maintainers)

Most upvoted comments

Maybe try with node --expose-internals script.js.

+20

silverwind on Feb 28, 2016

I hit this today using node v7.7.2 and I’m using babel-node so --expose-internals doesn’t work for me

mo on Jul 10, 2017

Too bad it’s closed without clear solution. I’ve just hit the same wall 😞

4O4 on Dec 4, 2017

i am affected on v7.7.3, the --expose-internals workaround worked for me, but process.binding('config').exposeInternals = true did not

maksimioffe on Jul 9, 2017