@Joey I couldn't pinpoint exactly which dependency caused this error. But I did a diff between my backup node_modules and the failed node_modules and mapped the dependencies that changed during the yarn install. This created a resolutions section in my package.json to record the dependency versions that changed from one node_module to the other. My resolutions in package.json looked like this: "resolutions": { "@grpc/grpc-js": "1.10.9", "protobufjs": "7.2.5", "@grpc/proto-loader": "0.7.13", "@js-sdsl/ordered-map": "4.4.2", "long": "5.3.2", "@protobufjs/aspromise": "1.1.2", "@protobufjs/base64": "1.1.2", "@protobufjs/codegen": "2.0.4", "@protobufjs/eventemitter": "1.1.0", "@protobufjs/fetch": "1.1.0", "@protobufjs/float": "1.0.2", "@protobufjs/inquire": "1.1.0", "@protobufjs/path": "1.1.2", "@protobufjs/pool": "1.1.0", "@protobufjs/utf8": "1.1.0" },