mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-12 17:45:49 +08:00
Jack Franklin
8f8ec22bb3
No changes in the changelog (https://github.com/karma-runner/karma/blob/master/CHANGELOG.md) to concern ourselves about, but one useful change is they upgraded the log4js dependency which was spitting out console messages on each test run. This is fixed with this version of Karma. Bug: none Change-Id: Ic49618cbda7a079cacb9813f5129692a83508a92 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3745621 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Commit-Queue: Philip Pfaffe <pfaffe@chromium.org>
12 lines
704 B
JavaScript
12 lines
704 B
JavaScript
const dns = require('dns')
|
|
|
|
// Node >=17 has different DNS resolution (see
|
|
// https://github.com/nodejs/node/issues/40702), it resolves domains
|
|
// according to the OS settings instead of IPv4-address first. The Karma server
|
|
// only listens on IPv4 address (127.0.0.1) by default, but the requests are
|
|
// sent to `localhost` in several places and `localhost` is resolved into IPv6
|
|
// address (`::`). So the run/stop/proxy request is unable to reach the Karma
|
|
// server and produces an error. To mitigate this issue karma force the
|
|
// IPv4-address first approach in Node >=17 as well.
|
|
module.exports.lookup = (hostname, options, callback) => dns.lookup(hostname, { ...options, verbatim: false }, callback)
|