First, both libraries put some variant of this information in theuser-agent header, or at least they're supposed to. Does that resolve your problem of wanting that information in a header?

Second, library users can already dorequire('grpc/package.json') orrequire('@grpc/grpc-js/package.json') and then format the information from that however they want.

Libraries usegrpc/${version} header.@JustinBeckwith can know more about tracking and ifuser-agent header is sufficient. Justin, do you know if can we go withuser-agent and not setgrpc at all?

As for the second item, it won't be possible since the gax code can accept anygrpc instance from the caller and it does not know if it's one or another implementation.

If the currentuser-agent behavior does not solve your problem, this change needs to go through ourAPI design review process because it is a (non-breaking) API change.

I don't think it's a good idea to export this information pre-formatted for a specific use-case. I would prefer to either export the wholepackage.json as a single object or exportname andversion verbatim.

I'm totally fine with either of those options - I just wanted to have the conversation started :)