The old grpc package is being depcrated and a new package @grpc/grpc-js is the replacement. This is pretty much an in-place replacement and does not break anything for us. However, since we had created some wrappers - the signatures for these needed updating.
An added benefit with this PR is that we will also then be able to more easily bundle backends with tools like WebPack and get a small footprint as the original Grpc package has a binary dependency that it needed and was hard to properly bundle.
At the same time I've also made all the samples work again. It was inconsistent on tenant setup - made it all consistently use the development tenant.
The old grpc package is being depcrated and a new package @grpc/grpc-js is the replacement. This is pretty much an in-place replacement and does not break anything for us. However, since we had created some wrappers - the signatures for these needed updating.
An added benefit with this PR is that we will also then be able to more easily bundle backends with tools like WebPack and get a small footprint as the original Grpc package has a binary dependency that it needed and was hard to properly bundle.
At the same time I've also made all the samples work again. It was inconsistent on tenant setup - made it all consistently use the development tenant.