andrewweston

This is the installation step we use (Codespaces runs in a Docker container): ``` ARG PB_WEB_VERSION RUN curl -LO "https://github.com/grpc/grpc-web/releases/download/protoc-gen-grpc-web-${PB_WEB_VERSION}-linux-x86_64" \ && mv protoc-gen-grpc-web-${PB_WEB_VERSION}-linux-x86_64 /usr/local/bin/protoc-gen-grpc-web \ && chmod +x /usr/local/bin/protoc-gen-grpc-web...

Yes, it is a typo. It should have been `--proto-path`, not `-proto-path`.

And yes, it does seem very much like an environment issue. We've been using the `grpc-web` plugin locally for about 1 year with no issues.

The thing that led me to believe the issue is with `protoc-gen-grpc-web` is that `protoc` works by itself (generates a `js` file) whereas it stops when I add the plugin....

That's what I thought too. I've checked and `uname -a` returns: ``` Linux codespaces_3d2e7f 5.4.0-1055-azure #57~18.04.1-Ubuntu SMP Fri Jul 16 19:40:19 UTC 2021 x86_64 GNU/Linux ```

I'll see what I can do to reproduce using a simple Docker in Docker set-up. I might not get to get for a few days...

I have a similar rule-based formatting issue. The rule works until I add the `include` property and then it stops being applied. It will work as expected if I use...