proto-loader | Protocol Buffer loader module for webpack | Command Line Interface library

I am facing an issue when I am trying to create a grpc client call using node js. when I use import "google/api/annotations.proto" in proto file I get an below error. if I remove it it works file. May I know what I am missing from my client.js

Error: unresolvable extensions: 'extend google.protobuf.MethodOptions' in .google.api at Root.resolveAll (src/github.com/workspace/explorer/node_modules/protobufjs/src/root.js:255:15) at Object.loadSync (/src/github.com/workspace/explorer/node_modules/@grpc/proto-loader/build/src/index.js:224:16) at Object. (/src/github.com/workspace/explorer/server/grpc/client.js:3:37)

I am trying to use GRPC with TypeScript, and I am trying to make sure I have all the types set (rather than just adding my own mapping or using any.

I've gotten as far as with problems I am experiencing noted in the comments.

I was doing a proof of concept on gRPC using node.js

Here is my package.json

I have a gRPC server implemented in python and I am calling an RPC from NodeJS but it gives an error "Method not found". When I call using the python client, the request is successful.

I'm trying to start a server daemon from within my js code, then to access it from the same program. However, when I use the execFile() method from the child_process module, this blocks the entire program: the execFile() call never stops, and I am unable to access the server. However, I know the daemon is started since I see a process of the same name start up from my activity monitor (macos equivalent of task manager).

I've also tried exec() and spawn() from the same module, and it gave the same results.

What I'd want to be able to do is to start the daemon as a separate process, forget about it, then stop it when I'm done using it. Is there any way I could do at least the first two?

Here is my code (the runArduino function is where I start the daemon, and the main() function is where I access it):

I'm trying to load .proto files coming from the arduino-cli repo. More specifically, I'm loading the commands.proto that has a dependency on a few other .proto files within the same directory.

In the load options provided to proto-loader, I specified the paths to all these .proto dependencies, yet an error pops up stating that proto messages defined in one of these dependencies are not defined.

Here is my code:

I created a really simple bookstore with a Books, Customer, and a main service. This particular problem involves the main and books service.

I'm currently making a gRPC request called: "createBook", which creates a book in our DB, and also console logs.

When running the gRPC server (booksServer) without docker, the process runs smoothly.

But as soon as I use docker, it seems as if a gRPC request doesn't go into the gRPC server...

By "using docker" I mean using docker to run the booksServer. (As shown below)

Result: Without Docker

I want to transmit a sample video file from backend grpc service to the browser using grpc-web, I did some tweaks based on official hello world tutorial. Btw, nothing changed in the envoy configuration. The video file is split into 17 chunks, I can receive 17 messages in browser, however there is nothing inside, what should do so I can get the data?

protobuf definition:

New to gRPC, I'm trying to stream a video file using grpc, both client and server are in Node, when running the service, I can console log the buffer on the server side, however I can't get anything from client side, Could anyone help me out, thanks!

video.proto: