Future Roadmap of Typescript Definition Generation
- Dominant language
- JavaScript
- Stars
- 9.3k
- Forks
- 802
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 5
Description
👋 Hello, I'm one of the maintainers of ts-protoc-gen, we are currently [considering the future of our package in an RFC](https://github.com/improbable-eng/ts-protoc-gen/issues/145) and would appreciate your thoughts on the following topic which will help us steer our own roadmap.
As part of considering the future of ts-protoc-gen, we are thinking that it would benefit the wider TypeScript community to split ts-protoc-gen into 2 separate plugins:
a) a protoc plugin dedicated to generating service stubs for use with [improbable-eng/grpc-web](https://github.com/improbable-eng/grpc-web) clients.
b) a protoc plugin for generating the TypeScript definitions to accompany the messages generated by protoc's JavaScript language support (which can be used by any TypeScript project regardless of which (if any) grpc service implementation is being used).
It's great that `protoc-gen-grpc-web` provides support for generating Typescript definitions for both messages and services, however if the TypeScript definition generation was moved up into protoc itself, or extracted into a separate plugin then we would no longer need to create and maintain plugin B mentioned above.
I'd love hear your thoughts on this and see if we can combine efforts to provide a more unified, and flexible set of tools for TypeScript developers
Contributor guide
Assessment
This issue has not been assessed yet.