Support ESM named exports

[vadistic]

Did you read the migration guide?

- [ ] I have read the whole migration guide

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Potential Commit/PR that introduced the regression

No response

Versions

9.1.1

Describe the regression

Exactly the same issue as nestjs/nest#8320 for core packages

For core packages upgrade to 8.1.1+ fixes it, for nestjs/graphql - current verison 9.1.1 still hast this issue.

import { Query, Resolver } from '@nestjs/graphql';
         ^^^^^
SyntaxError: Named export 'Query' not found. The requested module '@nestjs/graphql' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '@nestjs/graphql';
const { Query, Resolver } = pkg;

Minimum reproduction code

import { Query, Resolver } from '@nestjs/graphql'

in project with package type: "module" and target: "esnext"

Expected behavior

Node ESM named import works.

Other

I did not see the issue about it 🤷‍♂️

[moshest]

This should fixed that: microsoft/TypeScript#47070

Maybe release an updated version now with the latest TypeScript compiler?

[BenSjoberg]

@moshest Unfortunately, that fix hasn't landed in a stable TypeScript release yet, so updating won't help. Thankfully it looks like it'll make it into 4.6 (I just tried it in the latest 4.6 dev build) but that's not scheduled to come out until late next month.

[rhnorskov]

TypeScript 4.6 has now been released, perhaps it worth reopening this issue?

[kamilmysliwiec]

PR should be auto-created shortly

[moshest]

Still not working for me at version 10.0.6:

SyntaxError: The requested module '@nestjs/graphql' does not provide an export named 'Args'

[michael-land]

it would be nice @nestjs/apollo support esm too