Client typescript errors

[dan2kx]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Network project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

I'm using @ory/keto-grpc-client with typescript and i am seeing compiler issues in some files...

node_modules/@ory/keto-grpc-client/ory/keto/relation_tuples/v1alpha2/write_service_grpc_pb.d.ts
node_modules/@ory/keto-grpc-client/ory/keto/relation_tuples/v1alpha2/check_service_grpc_pb.d.ts
node_modules/@ory/keto-grpc-client/ory/keto/relation_tuples/v1alpha2/expand_service_grpc_pb.d.ts
node_modules/@ory/keto-grpc-client/ory/keto/relation_tuples/v1alpha2/read_service_grpc_pb.d.ts

Cannot find module 'grpc' or its corresponding type declarations.

import * as grpc from "grpc";

I think maybe those should be importing from "@grpc/grpc-js" instead?

Additionally,

node_modules/@ory/keto-grpc-client/ory/keto/relation_tuples/v1alpha2/index.d.ts:11:3 - error TS2666: Exports and export assignments are not permitted in module augmentations.

node_modules/@ory/keto-grpc-client/index.d.ts:4:3 - error TS2666: Exports and export assignments are not permitted in module augmentations.

Here is my tsconfig file,

{
  "compilerOptions": {
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "lib": ["esnext"],
    "module": "commonjs",
    "moduleResolution": "node",
    "outDir": "./dist",
    "rootDir": "./src"
    "sourceMap": true,
    "strict": true,
    "target": "es5"
  },

  "include": ["src/**/*"],
  "exclude": ["node_modules", "dist"]
}

Reproducing the bug

Create typescript project and use tsc command to build

Relevant log output

No response

Relevant configuration

No response

Version

0.11.0-alpha.0

On which operating system are you observing this issue?

None

In which environment are you deploying?

None

Additional Context

I can overcome the issue for now by adding skipLibCheck: true, but i would prefer to not have to do that long term