Timo Stamm

Just noticed: The warning also appears for `vue`.

The warning also appears for `vue`.

Thanks for the issue! It's certainly possible to avoid a lot of allocations and copies. - Uint8ArrayList keeps a reference of chunks and defers concatenation. - GrowableUint8Array allocates legroom in...

I gave [resizable ArrayBuffer](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer/resizable) a shot. It performs really well, but we can get similar results with optimized allocations (see https://github.com/connectrpc/connect-es/pull/1530), and don't need to maintain two code paths (for...

Closing, but please feel free to re-open with a reproducible example.

Here's how it looks for me: ``` ➜ test node --version v18.15.0 ➜ test npm i @protobuf-ts/protoc added 1 package, and audited 2 packages in 949ms found 0 vulnerabilities ➜...

Each run checks for the latest version, unless a specific version is provided in package.json (see the readme). That's easy enough to do on a plane or during an internet...

Thanks for the detailed report, Evan. This looks to be a similar issue that Svelte used to have, where universal load functions would fail to serialize pre-fetched requests with a...

Thanks for opening the issue, Andrew! I'm not sure that the generated types should be modified by protovalidate rules. There's no guarantee that a given message has been validated before...

This is available since [v2.5.0](https://github.com/bufbuild/protobuf-es/releases/tag/v2.5.0). See the manual on [Valid types](https://github.com/bufbuild/protobuf-es/blob/v2.5.2/MANUAL.md#valid-types), and the [protovalidate-es example](https://github.com/bufbuild/protovalidate-es/blob/main/packages/example/src/valid-types.ts).