Skip to content

How do I get on the latest version of @grpc/grpc-js? #789

@bcoe

Description

@bcoe

Over the past few weeks there were a few bad releases of @grpc/grpc-js that went out the door, and effect the behavior of @google-cloud/pubsub, and other libraries that rely on grpc.

There is now a version of @grpc/grpc-js available, 0.6.9, which has addressed a variety of stability issues.

Getting on the new version

  1. in your project that uses @google-cloud/pubsub (@google-cloud/logging, etc), delete package-lock.json.
  2. delete your node_modules/ folder, so that you will receive a fresh install.
  3. npm install.
  4. npm ls 👈 look at this tree, it should indicate that you are on up-to-date versions of @grpc/grpc-js, if not let us know and we can help.

What if I don't want to remove my package-lock.json?

As an alternative, you may also be able to run npm update @grpc/grpc-js, afterwards run npm ls, and confirm that all copies have been updated appropriately.

see #770

@npomfret, let me know if you bump into any issues with this upgrade process, and I can help debug here.

Metadata

Metadata

Assignees

Labels

api: pubsubIssues related to the googleapis/nodejs-pubsub API.type: questionRequest for information or clarification. Not an issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions