deploy full ESM with "type": "module" in "latest-esm" npm tag

[PabloSzx]

I also just re-published graphql@16.0.1 as graphql-esm@16.0.1 https://npm.im/graphql-esm, tested it in an example project using libraries with full ESM support https://github.com/PabloSzx/test-graphql-esm, everything works perfectly 👌

It can be tested right now doing this:

{
  "dependencies": {
    "graphql": "npm:graphql-esm@^16.0.1"
  }
}

[IvanGoncharov]

Please add integrationTests/esm for this package.
Try to test as many esm-specific things as possible.

[IvanGoncharov]

Also please ensure that this package works with upcoming TS 4.5 that should support esm natively and add integration tests for that.

[yaacovCR]

Looks good to me!

looks like esm tag makes sense out of band from canaries and all that

[yaacovCR]

Looks good to me!

looks like esm tag makes sense out of band from canaries and all that

@IvanGoncharov is this ready for re-review?

[github-actions]

@github-actions publish-pr-on-npm

@IvanGoncharov The latest changes of this PR are available on NPM as
graphql@17.0.0-alpha.1.canary.pr.3361.04ab27334641e170ce0e05bc927b972991953882
Note: no gurantees provided so please use your own discretion.

Also you can depend on latest version built from this PR:
npm install --save graphql@canary-pr-3361

[IvanGoncharov]

I rebased this PR to the latest main as the solution for #3603

[yaacovCR]

@IvanGoncharov @PabloSzx et al

question about the current state => the build scripts add a build qualifier of "+esm" and a tag suffix of "-esm", but do not rename the package to graphql-esm => the integration tests that use graphql-esm just point to a local tarball with the distribution, presumably where the name of the package is still graphql.

Over at the graphql-esm on npm -- it doesn't seem like we have used the exact machinery within this repo to publish as on npm graphql-esm is up to 16.5 and the tag is just 'latest' not 'latest-esm'.

So, where are we with this? Some options:

(1) we can get rid of the build qualifiers and tag suffix, and have a package name suffix of "-esm" and every time we publish to graphql, we should also publish to graphql-esm....
(2) we can get rid of the cjs version and also get rid of the build qualifiers and tag suffix.

So either way, the end goal will be to get rid of the build qualifier and tag suffix, right?

But have we decided on what will happen?