(introspection) - Fix usage of executeSync causing invalid mjs import

[kitten]

Fix #2250

Summary

Resolves an issue where the old version of babel-plugin-modular-graphql wasn't warning us forcefully about executeSync not being present in all versions we support, which resulted in it being imported from "graphql", which then instantiates non-mjs duplicate modules in some versions of Node.js (i.e. when Node isn't in ESM mode)

Set of changes

• Replace executeSync with execute

This release will simply then cause a rebuild and re-release with [email protected]

[changeset-bot]

🦋 Changeset detected

Latest commit: dc8d51e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@urql/introspection	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[CherryDT]

(i.e. when Node isn't in ESM mode)

Hm, in my issue I was on node 16 and had "type": "module" in my package.json so it should be in ESM mode, shouldn't it?

[kitten]

@CherryDT Yup, on a second check, you're right. I must've done something wrong in debugging and it indeed interprets it as CJS always. I believe the issue is that graphql@16 still doesn't come with a package.json:exports entry. I really thought it did but I was mistaken, so this won't work regardless of the Node.js mode and is rather caused by being in ESM mode, not by not being in it 😆