"moduleResolution": "Node16" default/named export bug

Reproduction example

Note: unable to provide a codesandbox link due to the inability to control the version of TypeScript used by the IDE

Prerequisites

1. typescript@4.8.3
2. @testing-library/user-event@14.4.3
3. package.json type: module
4. tsconfig moduleResolution set to Node16

// tsconfig
{
  "compilerOptions": {
    "target": "ESNext",
    "module": "ESNext",
    "moduleResolution": "Node16"
  }
}

Expected behavior

userEvent should be the default export of the module

import userEvent from "@testing-library/user-event";

userEvent.click(...);

Actual behavior

userEvent is exported as a named export called default

import userEvent from "@testing-library/user-event";

userEvent.default.click(...);

User-event version

14.4.3

Environment

Testing Library framework:

JS framework:

Test environment:

DOM implementation:

Additional context

This may be invalid for Node 16's ESM spec.

I suspect changing it to the following will resolve the issue:

import {userEvent} from './setup';
export default userEvent;

Start with src/index.ts at the linked export and compare it with the referenced ./setup module. Reproduce the default-versus-named export behavior using TypeScript 4.8.3, Node16 module resolution, and @testing-library/user-event 14.4.3; done means the documented default import exposes click directly without .default.