There are examples how to run in a browser, but they typically involve a sidecar proxy. Here is one example:
Browsers present two challenges to gRPC. First, they only use HTTP/2 when using TLS or SSL, which a lot of websites don't. Second, Browsers don't expose the HTTP trailers that are needed to tell when the response is done. To get around these issues, we have gRPC-Web protocol, which modifies the gRPC protocol slightly to be usable on HTTP/1.1. The fetch() API for Browsers was supposed to fix the latter problem, but it has not been implemented by them, so we are kinda stuck with the work around until they do.
Lastly, browsers use CORS when making RPCs across origin, which happens when you serve your RPCs from a different port than you HTML. This may affect you depending on your setup.
I guess all of this is to say that getting requests (or RPCs) to work in the browser is much more complicated that it first appears, and unfortunately we can't fix it for you. The proxy solution, while more complex, does solve a number of things you would have to otherwise do.