Generated operations files don't include *.js extension in ESM project

[JumBay]

I did follow the doc here https://the-guild.dev/graphql/codegen/docs/getting-started/esm-typescript-usage, but the generated file don't include *.js extension in the import line

Here is my test repository https://github.com/JumBay/test-codegen and the codegen config file
https://github.com/JumBay/test-codegen/blob/main/.graphqlrc.yml.

If anyone see what's wrong?

[ardatan]

@JumBay Codegen configuration in .graphqlrc.yml should be under codegen:.
So it needs to be;

documents:
  - ./src/**/*.graphql
extensions:
  codegen:
    emitLegacyCommonJSImports: true
    generates:
      ./src/generated/types.ts:
        plugins:
          - typescript
          - typescript-operations
      ./src/:
        preset: near-operation-file
        presetConfig:
          extension: .generated.ts
          baseTypesPath: generated/types.ts
        plugins:
          - typescript-operations
          - typed-document-node

[JumBay]

Thanks it works.
What's confusing is that sometimes the doc refers to a YAML config file where errors aren't shown, or most of the time a typescript config one, but doesn't seem to work with esm and multiproject and using the typescript config disable autocomplete in vscode... So it's not that easy to setup codegen, but once it works, it's great :)

[saihaj]

What's confusing is that sometimes the doc refers to a YAML config file where errors aren't shown, or most of the time a typescript config one,

we are trying to move everything to use TS config. It has better TypeSafety and less prone to error which with yaml are so easy to make