Module '@graphql-tools/schema' cannot be imported using this construct. The specifier only resolves to an ES module, which cannot be imported synchronously. Use dynamic import instead.ts(1471)

[purrplingcat]

Hi,

I am using graphql-tools in my propject with typescript which uses module resolution node16 in my tsconfig.ts. I am using yarn PnP instead of standard node_modules.

{
  "target": "ES2020"
  "module": "commonjs", 
  "moduleResolution": "node16"
}

If I use the node module resolution, it works, but I can't use my exports in package.json in my other projects in workspace. When I use node16 as module resolution, I can use my exports, but I can't use the grpah-ql tools, because i got:

Module '@graphql-tools/schema' cannot be imported using this construct. The specifier only resolves to an ES module, which cannot be imported synchronously. Use dynamic import instead.ts(1471)

It is just TypeScript error, if I use node's require() it works. If I try to rewrite it to dynamic import, it fails due to PnP and dynamic import in node requires full-qualified name including suffix:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@graphql-tools/schema' imported from /home/ellen/source/repos/senses/packages/roztoky/dist/index.js
Did you mean to import @graphql-tools-schema-virtual-d6c21fd7dc/0/cache/@graphql-tools-schema-npm-8.5.0-562da82f9d-8eeefdd66e.zip/node_modules/@graphql-tools/schema/cjs/index.js?

and that looks pretty awful.

How can I force TypeScript to use standard import (synchronyous) to import @graphql-tools/schema? Thanks

[n1ru4l]

Hey @purrplingcat, do you think you can provide a minimal reproduction of this issue as a GitHub repository? As far as I know, we conform with the exports map as required by TypeScript (moduleResolution node16).

I quickly tried this (using yarn@1) and everything seems to work as expected: https://github.com/n1ru4l/graphql-tools-schema-node16-repro

We are not that versed in PNPM, to exclude that this is a pnpm issue can you please test whether the same issue also occurs when using yarn v1 or npm?

[purrplingcat]

I tried use standard node_modules, nothing changed, I still got the same TS error. I think this is caused by TypeScript and their problem with resolving dependencies which has declared type field to module in package.json as the graphql tools has. When I removed the type field in your graphql-tools package.jsonm it started work, but it's not solution, because when I install dependencies with yarn it is replaced by original packages.json file.

Btw: I am using yarn@3 and my project can't work with older version or without PNP.

[n1ru4l]

Please provide a minimal repeoduction that causes this error. Otherwise, we cannot help you, sorry.

[purrplingcat]

https://github.com/purrplingcat/typescript-module-error

[ardatan]

Could you create a more minimal example on CodeSandbox or StackBlitz?

[benasher44]

We're having this issue as well, only with @graphql-tools/* packages. Maybe it has something to do with ordering in the package.json? microsoft/TypeScript#49299

[benasher44]

Some quick screenshots to highlight the issue:

[n1ru4l]

@benasher44 Hey, can you please check and confirm whether the following versions #4624 (comment) resolve the issue?

[benasher44]

Sure! Just checked, and it's still an issue. I have updated the CodeSandbox, and it still reproduces there as well (checked there and local project). Thanks for your work on this! 🙏

[n1ru4l]

@benasher44 The code sandbox UI does not seem to use a recent version of TypeScript... Can you please modify this repo with a reproduction and then submit an issue here on the repository? https://github.com/n1ru4l/graphql-tools-commonjs-import-repro

To me it seems like everything is just fine there.

[benasher44]

It turns out that having a paths key in our tsconfig was triggering it still. After removing that (must be old config we no longer need) + this fix, it's working. Thanks for your help and fix!