Is this still maintained?

[steevhise]

Just wondering if anybody is still maintaining this.

There's a security issue because mocha-chrome depends on an old version of minimist.

├─┬ mocha-chrome@2.2.0
│ └─┬ chrome-launcher@0.11.2
│   └─┬ mkdirp@0.5.1
│     └── minimist@0.0.8

[shellscape]

Afaik this package is pretty obsolete. If you're using it and need a dep update, please submit a PR and I'll publish a new version.

[alehuo]

I have made a PR to make this library compatible with Mocha v10. See #48

This package hosts hundreds of tests in an open source project, and it's mission critical for us to keep this library up to date. We are on the process of migrating our Mocha tests to Playwright.

[p2edwards]

If you encounter this ECONNREFUSED ::1 error running mocha-chrome 2.2.0 in GitHub CI on Node >=17:

Promise Rejection:  Error: connect ECONNREFUSED ::1:39193
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '::1',
  port: 39193
}

This might help:

diff --git a/node_modules/mocha-chrome/lib/client.js b/node_modules/mocha-chrome/lib/client.js
index 7629126..cd3d163 100644
--- a/node_modules/mocha-chrome/lib/client.js
+++ b/node_modules/mocha-chrome/lib/client.js
@@ -9,7 +9,7 @@ module.exports = async function connectClient(instance, log, options) {
     return fs.readFileSync(filePath, 'utf-8');
   }
 
-  const client = await CDP({ port: instance.port });
+  const client = await CDP({ port: instance.port, host: '127.0.0.1' });
   const { DOM, DOMStorage, Console, Network, Page, Runtime } = client;
   const mochaOptions = `window.mochaOptions = ${JSON.stringify(options.mocha)}`;

• More notes in my commit message here: https://github.com/kobotoolbox/kpi/blob/f587a1e4b5f4225442f8bf5f91a857de25d140da/patches/mocha-chrome%2B2.2.0.patch ¹²

Footnotes

1. Thanks to @nsainaney for this comment:

   With Node 16, DNS.lookup would return a IPv4 address. With Node 17 it returns an IPv6 address, which will break most REST clients that hardcode URLs like http://localhost:4040/api if the upstream server only binds to the IPv4 address, e.g. server.listen('127.0.0.1').

   ↩

2. npm.im/patch-package ↩