-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle google protobuf well known types #47
Comments
I've looked in to this a bit. I've worked around it with a symlink in the root of my repo:
|
Just wanted to point grpc/grpc-node#103 has been closed with the addition of @grpc/proto-loader and thus this issue can be fixed I believe. |
Hhm, I still have this issue as of today :( |
facing the same issue as well
|
I started working on a fix, using |
@claudiocabral I built on your start and finished it off with #61 |
I have also created a docker image with built in common protobuf includes here which includes the |
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 '...' in './foo.proto': file not found
error.These well-known types should be handled automatically by importing them from the protobuf npm package instead.
The text was updated successfully, but these errors were encountered: