Any way to mitigate dist size growth
Open
- Dominant language
- JavaScript
- Stars
- 9.3k
- Forks
- 802
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 5
Description
Hey,
I've been playing about with grpc-web and there some threads around the [dist size](https://github.com/grpc/grpc-web/issues/270) already, but their concern was around the base dist using the lightweight hello world example.
Is there a best approach to combating the dist size as the needs grow? E.g. You're defining 300 messages and beyond?
Based on the generated client code so far, I'm guessing all defined messages are linked to the generated code and are included in the dist regardless?
Contributor guide
Assessment
This issue has not been assessed yet.