Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Cannot read property 'indexOf' of null #21

Closed
ghost opened this issue May 17, 2017 · 2 comments
Closed

TypeError: Cannot read property 'indexOf' of null #21

ghost opened this issue May 17, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented May 17, 2017

Node v7.7.2
why-is-node-running: npm 1.2.2

The error seems to happen here.

There are 1 known handle(s) keeping the process running and 3 unknown
Known handles:


C:\Initech\node_modules\why-is-node-running\index.js:69
  known.forEach(function (obj, i) {
        ^
TypeError: Cannot read property 'indexOf' of null
    at C:\Initech\node_modules\why-is-node-running\index.js:73:29
    at Array.filter (native)
    at C:\Initech\node_modules\why-is-node-running\index.js:72:21
    at Array.forEach (native)
    at module.exports (C:\Initech\node_modules\why-is-node-running\index.js:69:9)
    at Timeout._onTimeout (C:/Initech/build/gulp/gulpfile.es:249:22)
    at ontimeout (timers.js:380:14)
    at tryOnTimeout (timers.js:244:5)
    at Timer.listOnTimeout (timers.js:214:5)
@chrisl8
Copy link

chrisl8 commented Nov 30, 2017

@errorx666 Your fix works. Thank you!

jollytoad added a commit to jollytoad/why-is-node-running that referenced this issue Jan 12, 2018
@mafintosh
Copy link
Owner

should be fixed in latest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants