Re: [grpc-io] grpc-web: Separate libraries per proto file (even though one imports the other)?

This is probably a scenario that's not supported by grpc-web at the moment. You are expected to have to compile B.proto in when you are trying to compile A.proto. There currently is no option to make compiling A.proto aware that there's a separate package for B already. This could be a future

[grpc-io] grpc-web: Separate libraries per proto file (even though one imports the other)?

I have a grpc-web question also posted on StackOverflow , but this seems like a better place to post it. How do I properly generate JS stubs for A.proto that imports B.proto, where there is already a