Stephen Haberman

Ah nice! Thanks for both the self-diagnosis and also reporting back the "pin to `@grpc/proto-loader` 0.6.13" fix @TannerPerrien !

:tada: This issue has been resolved in version 1.167.9 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/ts-proto/v/1.167.9) - [GitHub release](https://github.com/stephenh/ts-proto/releases/tag/v1.167.9) - `v1.167.9` Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

Late reply, but right @mvniekerk the `Exact` type was introduced in v1.91.0 but can be disabled with `--ts_proto_opt=useExactTypes=false` if it causes issues in your output.

I've merged #882 that: a) upgrades ts-proto's internal usages of `long` (for reading protobuf descriptors) to long v5 b) changes the non-`esModuleInterop` to use the `import Long = require("long")` syntax,...

@val-o I'm traveling so don't have time to fully remember/study the issue, but iirc / kinda guessing that @Vilsol 's PR from last year fixes this: https://github.com/stephenh/ts-proto/pull/484/files#diff-ad74198e9093dc9e981de421c0e333bb02e31091258228b27ec0dfe1932815a0R279 And we just...

Fwiw, per an earlier update, I'm 95% sure this has been fixed b/c ts-protos own/internal `ts-proto-descriptors` library that we use for reading messages from the protoc compiler handles `oneofIndex` being...

Hm, @slinkydeveloper are you using the `usePrototypeForDefaults` option? The `oneof_index` in your bug report is exactly what we had to handle too, although now I'm wondering if we handled the...

We've had a lot of changes/flags added optional fields since this ticket was filed, and #1007 just added support for proto2 optional values, so going to kind of lazily assume...

An `outputIndex` option was added in #821

Fwiw I think with #762 the wrapper types of `Timestamp` and `Struct` / `Value` / `ListValue` should be working in NestJS, so I'm going to close this out. Feel free...