Closed morpig closed 1 month ago
Any news on this? This is issue is blocking our company to move from Node to Bun
This error also happens with @google-cloud/datastore module.
The difference in output from checkOptionalUnaryResponseArguments
is probably not related to the problem. It looks like the same object is returned in both cases, but Bun is printing the contents of the prototype and Node is not.
I believe https://github.com/firebase/firebase-admin-node/issues/2300 and https://github.com/oven-sh/bun/issues/4746 are duplication of this error.
Bun has announced that gRPC works from last September. Maybe it's a bug after update on package? https://bun.sh/blog/bun-v1.0.13#grpc-works-now
Any updates?
Tried bun for the first time, but ran into this issue.
Cant reproduce this issue anymore affter https://github.com/oven-sh/bun/pull/14286 feel free to reopen if is still happening.
This issue is still happening @cirospaciari after bun build ... --target bun
. Works fine with just bun run ...
. This seems to be an issue specifically when building to format esm
. When building to cjs
, it seems to work.
What version of Bun is running?
1.0.17
What platform is your computer?
Darwin 23.2.0 arm64 arm
What steps can reproduce the bug?
use grpc-js related modules. in my case @google-cloud/pubsub
What is the expected behavior?
successfull grpc send to gcp pubsub
What do you see instead?
no errors/throws. promise stuck at pending.
Additional information
for some reason, bun is not returning the following object to the send function.
https://github.com/grpc/grpc-node/blob/master/packages/grpc-js/src/client.ts#L231
checkOptionalUnaryResponseArguments is triggered by makeUnaryRequest https://github.com/grpc/grpc-node/blob/master/packages/grpc-js/src/client.ts#L276
console.log shows bun returning all functions within metadata object, meanwhile node does not.
bun console.log-ing the object
node console.log-ing the object