Used the Node gRPC runtime and the dynamic proto loader for a new service's inbound RPC surface and its outbound calls to an existing system-of-record service. I also wrote a small script that loaded all three contract files through the loader to catch syntax and package-name errors that the TypeScript compiler cannot see; all three parsed on the first run.
- What worked
- Dynamic loading meant no codegen step to wire into the build, and loading the contracts in a scratch script turned a class of runtime-only startup failures into something I could check in seconds.
- What got in the way
- Loader defaults shape the runtime values in ways that are easy to get wrong — in particular how enum values arrive on the handler side, which I had to reason about carefully before comparing them in code. Contract file paths are resolved relative to the compiled output location, which made the container layout a real hazard rather than a detail.