Generated service not showing up as type `ServiceType` about connect-es

[timostamm]

Hey Brenner, I copied your TypeScript config into our example and don't see an issue.

The cause of the error message you see is:

Type 'CreateBackfillJobRequest' is missing the following properties from type 'AnyMessage': equals, clone, fromBinary, fromJson, and 6 more.

This indicates that the base class Message from @bufbuild/protobuf could not be resolved when the compiler tries to compile the generated code.

You can remove the comment @ts-nocheck from the generated code to see an error message explaining why. (We generate the annotation for better BC, but it can be disable, see the documentation.)

I'm going to close this, but please feel free to re-open with a reproducible example.

[BrennerSpear]

My fix was adding - import_extension=.ts

I'm using turbopack for my bundler

version: v1
plugins:
  # This will invoke protoc-gen-es
  - plugin: es
    out: ./packages/shadow-protos
    opt:
      - target=ts
      - import_extension=.ts
  # This will invoke protoc-gen-connect-es
  - plugin: connect-es
    out: ./packages/shadow-protos
    opt:
      - target=ts
      - import_extension=.ts

[timostamm]

Thanks for posting the resolution, Brenner!

If you are using next.js, this is a known issue, see vercel/next.js#59744. If you are not using next.js, the same issue likely applies to turbopack.

The ecosystem is in a bad state right now: You have to use the .js extension in imports for TypeScript's modern ESM resolution logic, but bundlers are slow to catch up.

The option import_extension=.ts or import_extension=none should both work in this case.