wct: Does not work with Node 10 on Windows 10

[osamamaruf]

The below error is received on executing the following command wct --skip-selenium-install

TypeError: Cannot read property '1' of null

Actual Behavior

Test cases do not run.

Expected Behavior

Test cases should run

Versions & Environment

• Polymer CLI: v1.9.8
• node: v10.15.3 (Windows)
• npm: v6.4.1 (Windows)
• WCT v6.9.2
• Operating System: Windows 10
• Browsers Tested on : Chrome v.74

Downgrading to lower than node 10 works fine. See also (#3261 and #280)

[armujahid]

Same error is occurring even in WSL with node v12.

Windows version: Version 1903 (Build 18362.535)
WSL: Linux <hostname> 4.4.0-18362-Microsoft #476-Microsoft Fri Nov 01 16:53:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux
Node v12.13.1
Npm 6.12.1

Error:

$ npm run test

> polymer-starter-kit@4.0.0 test /mnt/d/polymer3freshfromlinux
> polymer test


TypeError: Cannot read property '1' of null

error: [cli.main]   cli runtime exception: TypeError: Cannot read property '1' of null
error: [cli.main]   TypeError: Cannot read property '1' of null
    at module.exports (/mnt/d/polymer3freshfromlinux/node_modules/polymer-cli/node_modules/promisify-node/utils/args.js:9:63)
    at processExports (/mnt/d/polymer3freshfromlinux/node_modules/polymer-cli/node_modules/promisify-node/index.js:61:29)
    at module.exports (/mnt/d/polymer3freshfromlinux/node_modules/polymer-cli/node_modules/promisify-node/index.js:164:10)
    at Object.<anonymous> (/mnt/d/polymer3freshfromlinux/node_modules/polymer-cli/node_modules/wct-local/lib/browsers.js:78:32)
    at Generator.next (<anonymous>)
    at fulfilled (/mnt/d/polymer3freshfromlinux/node_modules/polymer-cli/node_modules/wct-local/lib/browsers.js:4:58)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! polymer-starter-kit@4.0.0 test: `polymer test`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the polymer-starter-kit@4.0.0 test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/arm/.npm/_logs/2020-01-02T09_45_30_870Z-debug.log

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.