matchName throws TypeError: Cannot read property 'match' of undefined

[Narmdo]

I'm getting an issue caused by text within matchName being undefined.

Here's my stack trace.

    at o (...\node_modules\find-process\lib\find_process.js:25:1)
    at i.parseTable.filter (...\node_modules\find-process\lib\find_process.js:148:1)
    at Array.filter (<anonymous>)
    at ChildProcess.r.on (...\node_modules\find-process\lib\find_process.js:137:1)
    at ChildProcess.emit (events.js:182:13)
    at maybeClose (internal/child_process.js:962:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)

What would be causing this?

[mitchwilliamson]

I'm unable to reproduce this myself, but it is causing issues for some of our users.

We'll likely be resolving this by adding an undefined check in matchName in our own fork, but I'd imagine this is caused by a bug in the parsing of WMIC output in this library.

[Narmdo]

I'm doing exactly that right now. Couldn't replicate myself either, but have had several users have this issue.

[yibn2008]

I'll add an non-string check for matchName to avoid error