Add support for @grpc/grpc-js 1.x

[sk-]

Is your feature request related to a problem? Please describe.
I want to trace the execution of Firebase Functions using firestore. However the firestore clients use grpc-js 0.7.4, due to dependencies on google-gax 1.13.0.

Describe the solution you'd like
Support for grpc-js 0.7.4

Describe alternatives you've considered
I checked whether it would be possible to update the firestore client to the latest version, but that still uses google-gax 1.13.0, which depends on the grpc-js version mentioned earlier.

I also created googleapis/nodejs-firestore#1109 asking to update the dependency.

Additional context
Add any other context or screenshots about the feature request here.

[dyladan]

maybe @markwolff can weigh in here as he is the original plugin author. I assume there is some reason he only decided to support 1.x. This definitely depends on the level of effort needed to support it as 0.x is a pre-release version of grpc and I am hesitant to spend too much effort supporting old pre-release versions of modules.

[markwolff]

grpc-js is a re-write of grpc using pure javascript instead of relying on native modules, and was not recommended for production until a month ago with its 1.x release.

The action item here would be to write a new plugin for grpc-js. Only [email protected] should be supported, but judging from the release notes, there aren't any breaking changes from 0.x...1.x so both should be compatible.

https://www.npmjs.com/package/@grpc/grpc-js
https://www.npmjs.com/package/grpc

[dyladan]

If only 1.x is supported, it will fail to install on 0.x. We currently don't have a mechanism to force the installation to succeed on an incompatible version. Maybe we should? Obviously we would want to name the option something scary that makes it clear this is at your own risk.

[markwolff]

@dyladan I am confused. Are you referring to the plugin loader?

[dyladan]

Yes.

Only [email protected] should be supported, but judging from the release notes, there aren't any breaking changes from 0.x...1.x so both should be compatible.

If we create a plugin for grpc-js which only contains 1.x in the supported versions matrix, the plugin loader will not load it if you are using a version of grpc-js prior to 1.x

[markwolff]

Makes sense. @sk- if you want to contribute this you are welcome to. Else I can take this when I have some cycles.

@dyladan Do you think this plugin should live in this repo or live in contrib? It seems to be the supported grpc lib going forward now, and so I think it should take the place as the "grpc plugin" for this repo. The existing one could be moved to contrib and potentially become non-default as well.

[dyladan]

what do you mean "supported grpc lib"? I admit to being a little out of the loop on grpc related topics.

[markwolff]

A quick overview:

• grpc: grpc package which has existed for years. Written with native c++ addons. Stable, but doesn't seem to be getting updates anymore (past 6 months). It probably will get updated if the grpc protocol ever requires changes and so I don't think it is considered "unsupported". We have an opentelemetry plugin for this lib.
• @grpc/grpc-js: Re-write of grpc to use pure JS (nodejs) instead of relying on c++ stuff. Was in beta until past few weeks. No opentelemetry plugin exists for this yet.

The code for both of these packages lives here and grpc-js is now more popular than its predecessor and is receiving regular updates. The feature gap between the two is here