Jest detecting open handle when ran with ts-jest

[vajahath]

🐛 Bug Report

Jest detecting open handle when ran with ts-jest. Outside ts-jest, there is no problem. Please note I'm running typescript 4.

test.spec.ts

const got = require("got");

describe("Test", () => {
  test("got test", async () => {
    await got("https://google.com");
  });
});

jest.config.js

module.exports = {
  preset: "ts-jest",
  testEnvironment: "node",
  testMatch: ["**/src/**/*.spec.ts"],
};

➜ npm run test:ts -- test.spec

> jest --detectOpenHandles "test.spec"

 PASS  src/test.spec.ts
  Test
    ✓ got test (1166 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        3.214 s
Ran all test suites matching /test.spec/i.

Jest has detected the following 1 open handle potentially keeping Jest from exiting:

  ●  DNSCHANNEL

      at new CacheableLookup (node_modules/cacheable-lookup/source/index.js:75:14)
      at Object.<anonymous> (node_modules/got/dist/source/core/index.js:29:24)
      at Object.<anonymous> (node_modules/got/dist/source/as-promise/types.js:16:16)

envinfo

System:
    OS: Ubuntu 20

Npm packages:
    "ts-jest": "^26.3.0",
    "ts-node": "^9.0.0",
    "jest": "^26.4.2",
    "typescript": "^4.0.2"

[ahnpnl]

this happens to babel-jest too, not only ts-jest

[ahnpnl]

See jestjs/jest#6423