Add `"types"` entries to the `"exports"` property of `package.json`, to allow consumption from Typescript with the new `Node16` module resolution strategy

Is your feature request related to a problem? Please describe.

I’m unable to consume "@graphql-yoga/common" from Typescript 4.7, when module resolution is set to Node16

Describe the solution you’d like

Add "types" entries to the "exports" property of package.json

Describe alternatives you’ve considered

None

Additional context

The following should suffice

"exports": {
  ".": {
    "types": "./index.d.ts",
    "require": "./index.js",
    "import": "./index.mjs"
  },
  "./*": {
    types": "./*.d.ts",
    "require": "./*.js",
    "import": "./*.mjs"
   },
  "./package.json": "./package.json"
}

[n1ru4l]

@Duncan3142 This is now fixed in this release https://github.com/dotansimha/graphql-yoga/pull/1303 😇

@graphql-yoga/common@2.9.0

[Duncan3142]

@n1ru4l There is one more thing I noticed in the code for your PR which would result in divergent behaviour, though my previous comments still apply. The package.json in the root of your forked repo is missing "type": "module"

This means typescript will always treat .ts files as commonjs files, so imports in those files will always transpile to ‘require’. This would break the consumption of ‘@repeaterjs/repeater’

If the “type” field is missing or set to “commonjs”, typescript files need to have the .mts extension to be treated as ESM

The following links go into detail:

Typescript 4.7 File Extensions Typescript 4.7 Package Imports/Exports Node package docs