graphql/codegen/docs/getting-started/esm-typescript-usage

[giscus[bot]]

graphql/codegen/docs/getting-started/esm-typescript-usage

https://the-guild.dev/graphql/codegen/docs/getting-started/esm-typescript-usage

[LongLiveCHIEF]

Lately, I've been using tsconfig.json "module": "Preserve" instead of setting both module and moduleResolution to node16. (or nodenext).

It seemed like it was the only way to get the language server to play nice. Every other setting winds up causing the dreaded red squiggly on the generated imports.

On the other hand, I'm using tsx instead of running the tsc, so i'm not actually generating js files even when running things.

[LongLiveCHIEF]

my full tsconfig.json:

{
  "compilerOptions": {
    // Treat files as modules even if it doesn't use import/export
    "moduleDetection": "force",

    // Ignore module structure
    "module": "Preserve",

    // Allow JSON modules to be imported
    "resolveJsonModule": true,

    // Allow JS files to be imported from TS and vice versa
    "allowJs": true,

    // Use correct ESM import behavior
    "esModuleInterop": true,

    // Disallow features that require cross-file awareness
    "isolatedModules": true,
    "target": "ES2024"
  }
}