[meta] nodejs 17 compatibility issues

[rpl]

There are currently more than one issue that prevent web-ext run to fully work on nodejs 17, the main issue seems to be related to the default behavior of the dns resolution (see nodejs/node#40537 and nodejs/node#39987).

The following web-ext internals seems to have issues:

• ChromiumExtensionRunner
  • due to the ws url generated from the WebSocketServer's address and port not be in a valid format when address is an IPv6
  • due to chrome-launcher dependency trying to connect to IPv6 while Chrome is listening on IPv4
• FirefoxAndroidExtensionRunner
  • due to @devicefarmer/adbkit defaulting to an IPv6 adbHost, while adb is likely still listening on IPv4 (similarly to the chrome-launcher issue)

web-ext issues and pull requests

• web-ext run -t chromium (ECONNREFUSED after launching Chrome #2331)
  • fix(deps): update dependency chrome-launcher to v0.15.0 #2324
  • fix: Replace localhost with ipv4 to avoid ipv6 issue #2339
• web-ext run -t firefox-android
  • fix: Set default adb host to 127.0.0.1 to prevent localhost resolution mismatch in nodejs 17 #2360

upstream issues and pull requests

• chrome-launcher upstream issue: ECONNREFUSED with Node 17 GoogleChrome/chrome-launcher#251 (released as part of chrome-launcher v0.14.2)
• @devicefarmer/adbkit upstream issue: connection issue with nodejs 17 on system where localhost will resolve by default to an ipv6 address DeviceFarmer/adbkit#209

[eight04]

chrome-launcher issue:
GoogleChrome/chrome-launcher#251

[rpl]

@eight04 Thanks a lot for your help on investigating, reporting to the upstream repos, and fixing these nodejs 17 issues on web-ext side too, that was all very much appreciated ❤️

I included the fixes for the issues we are currently aware of in the 6.6.0 version that we have just released on npm, and so I'm going to close this meta issue as fixed (we can file new issue if we discover other issues that prevents web-ext to work correctly on nodejs 17).