Dynamic types based on proto definition

[Joel-PeakMetrics]

Dynamic types based on proto definition

[jcready]

Unlike protobuf.js, protobuf-ts depends on protoc for generating code. There is no way to directly convert the string content of a proto file into usable classes for encoding/decoding messages. You could potentially invoke protoc via a subprocess, but you'd still have to do everything via the file system (source files -> protoc -> out files -> await import('../some/out-file.ts')).

Additionally, protobuf-ts doesn't generate a single "root" (top-level proto package namespace) with messages indexed based on their package + message name. Instead it generates a number of files which match the file structure of the input proto files where each file exports message classes which match their proto message name (unless there is a naming conflict like having your proto file contain a message named const).