I am using grpc-web to communicate with a java backend over gRPC. I am using ReactJS on the frontend which uses grpc-web to interpret the protobuffers.
I am getting this strange error. My protos are correct ( I checked using a reflection tool called "bloom" so the backend is just fine) This somehow seems like an error internal to the grpc libraries I am using in ReactJS.
I get the following error:
TypeError: Cannot read properties of undefined (reading 'MethodInfo')
The above error points to my proto file: dashboard_services_grpc_web_pb.js
In this file, it point to this line
const methodInfo_DashboardService_userLogin = new grpc.web.AbstractClientBase.MethodInfo( ...... );
I have a hard time solving this because according to my understanding, grpc.web.AbstractClientBase
is something native to grpc-web
.
I have also reinstalled my node_modules in hopes that this is a version issue but no avail.
I am using grpc-web to communicate with a java backend over gRPC. I am using ReactJS on the frontend which uses grpc-web to interpret the protobuffers.
I am getting this strange error. My protos are correct ( I checked using a reflection tool called "bloom" so the backend is just fine) This somehow seems like an error internal to the grpc libraries I am using in ReactJS.
I get the following error:
TypeError: Cannot read properties of undefined (reading 'MethodInfo')
The above error points to my proto file: dashboard_services_grpc_web_pb.js
In this file, it point to this line
const methodInfo_DashboardService_userLogin = new grpc.web.AbstractClientBase.MethodInfo( ...... );
I have a hard time solving this because according to my understanding, grpc.web.AbstractClientBase
is something native to grpc-web
.
I have also reinstalled my node_modules in hopes that this is a version issue but no avail.
Share Improve this question edited Oct 15, 2021 at 10:01 Asma Rahim Ali Jafri asked Oct 14, 2021 at 12:53 Asma Rahim Ali JafriAsma Rahim Ali Jafri 1,3833 gold badges17 silver badges22 bronze badges 6 | Show 1 more comment2 Answers
Reset to default 10I had the same issue because I was using an old release of the executable protoc-gen-grpc-web
with respect to the current version of grpc-web
. Using version 1.3.0 for both solved the issue for me.
You can download the latest release of protoc-gen-grpc-web
here.
In my case it was happening after cache clear, because we had:
"grpc-web": "^1.2.1",
and it was installed version 1.3.0
I changed it to:
"grpc-web": "1.2.1",
and yarn
again to fix this issue!
npm cache clean --force
– Asma Rahim Ali Jafri Commented Oct 14, 2021 at 13:32