# Dgraph-js client builds from Jan-9-2023 through Jan-11-2023 include a bug via the grpc-js dependency **URL:** \ **Category:** App Development\ **Tags:** kind:bug\ **Created:** [January 12, 2023, 7:02pm UTC](https://discuss.dgraph.io/t/dgraph-js-client-builds-from-jan-9-2023-through-jan-11-2023-include-a-bug-via-the-grpc-js-dependency/18169 "2023-01-12T19:02:42Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Damon](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/damon/32/8589_2.png) [@Damon](https://discuss.dgraph.io/u/Damon)\ **Post date:** [January 12, 2023, 7:02pm UTC](https://discuss.dgraph.io/t/dgraph-js-client-builds-from-jan-9-2023-through-jan-11-2023-include-a-bug-via-the-grpc-js-dependency/18169/1 "2023-01-12T19:02:42Z")
Hi all. The dgraph-js library includes a dependency on the latest version of grpc-js, so when that library is updated in npm, a build will automatically pull in the new version. Unfortunately, the “latest” version of grpc-js was broken for two days, so please re-do any builds you may have executed in the 1/9 - 1/11 timeframe. Our understanding is that the gRPC connection is not kept alive properly, so node/js callers will stop working without any obvious reason. The broken dependency is grpc-js v 1.8.2, and it has this defect: [https://github.com/grpc/grpc-node/issues/2318](https://github.com/grpc/grpc-node/issues/2318) . grpc-js 1.8.3 fixes the bug and that version is now latest so will be included by npm. Everything should work properly now (post 1/11/23), but because the 1.8.3 release may have been rushed out as a critical fix without full testing, we suggest including this PR from the Leadr team (Thank you, Nick!) [https://github.com/dgraph-io/dgraph-js/pull/164](https://github.com/dgraph-io/dgraph-js/pull/164) which specifies a dependency on grpc-js 1.8.1 which is know to be stable.