The protobuf "well-known types" (https://developers.google.com/protocol-buffers/docs/reference/google.protobuf) are included in every language runtime, including the npm package (see protocolbuffers/protobuf#1638).

Currently, grpcc requires proto files that import a well-known type to have a copy of the well-known type locally, otherwise you get an `Error: failed to import '...

https://github.com/src-d/proteus/blob/master/ARCHITECTURE.md#protobuf-transformer:

Even though the step is transforming, it's inside the protobuf package to note that it's transforming the scanner.Package into a protobuf package.

Either you meant to say "it's important to note that...", or this is way too meta for me :)

See https://coveralls.io/builds/17797671/source?filename=ytypes%2Flist.go#L476 -- we have a number of error cases that we're not covering with existing tests. This issue tracks covering them.

Does the generated client code work with the Envoy proxy? I understand there may be some compatibility issues, particularly with regard to streaming services. Perhaps some sort of interoperability tests could be added.

The current API reference leaves a lot to be desired. Use modern tools to create something better.

Add sample Ionic app with code sharing between mobile app and webapp.

Instead on adding Ionic to the project, compare and add either Capacitor or Cordova to the project as a dev dependency, and configure a shell script tools/shell/build-mobile.sh th