URL behaves differently when run with jest

🐛 Bug Report

The object thrown by the constructor of URL is not an instance of Error.

To Reproduce

Create a file error.test.js with the following contents:

#!/usr/bin/env node
try {
  new URL("not_a_url");
} catch (anything) {
  process.exit(anything instanceof Error ? 0 : 1);
}

If you run node error.test.js the program exits successfully. However, if you use jest to run this file you get:

§ jest
  ●  process.exit called with "1"

      3 |   new URL("not_a_url");
      4 | } catch (anything) {
    > 5 |   process.exit(anything instanceof Error ? 0 : 1);
        |           ^
      6 | }
      7 |

      at Object.exit (error.test.js:5:11)

 RUNS  ./error.test.js

Expected behavior

I expect the error raised by the call to URL to be an instance of Error.

envinfo

  System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz
  Binaries:
    Node: 12.1.0 - /usr/local/bin/node
    Yarn: 1.22.0 - ~/.yarn/bin/yarn
    npm: 6.13.7 - /usr/local/bin/npm

[carsonreinke]

@lukasoppermann Something like const URLSearchParams = require('url').URLSearchParams, if you look at require('url') is actually this:

{
  Url: [Function: Url],
  parse: [Function: urlParse],
  resolve: [Function: urlResolve],
  resolveObject: [Function: urlResolveObject],
  format: [Function: urlFormat],
  URL: [Function: URL],
  URLSearchParams: [Function: URLSearchParams],
  domainToASCII: [Function: domainToASCII],
  domainToUnicode: [Function: domainToUnicode],
  pathToFileURL: [Function: pathToFileURL],
  fileURLToPath: [Function: fileURLToPath]
}

[SimenB]

This is #2549, yeah

@fredefox it is really strange, I have not really gotten to the bottom of it, but I did try using npmjs.com/package/jest-runner-mocha and it does NOT exhibit that behavior.

Yeah, this behavior is specific to Jest since we use the vm module to create sandboxes - mocha runs all the tests in the same context.

Latest update to #2549 is essentially https://github.com/nodejs/node/issues/31852