buf generate fails on windows with 'node_modules' is not recognized...

[connectrpc]

buf generate fails on windows with 'node_modules' is not recognized...

[timostamm]

Hey Alexandros, thank you for testing the approach via "scripts", I was about to mention this. npm and yarn will set up the path the executables automatically for you in scripts.

node_modules\.bin\protoc-gen-es is also an alternative (not the backslash instead of a slash), but it will not work cross-platform.

We will look into updating our documentation for this, thanks for the report!

[alexandros-megas]

Ok, so I'm not sure if this is just a me-issue, or a docs-issue, but after stumbling on this section in the protoc-gen-connect-web README (https://github.com/bufbuild/connect-web/tree/main/packages/protoc-gen-connect-web#with-protoc), I did a bit more experimentation and was able to fix this with the following:

1. Add a new script to my package.json: "bufgen": "buf generate"
2. Change the two path properties in buf.gen.yaml to be just the name of the executable script. eg path: protoc-gen-es and path: protoc-gen-connect-web.
3. Run the npm/yarn script: yarn bufgen

Gives the following output:

> yarn bufgen
yarn run v1.22.18
$ buf generate
Done in 3.29s.

[smaye81]

Updated our docs to more prominently suggest the "scripts" approach. In addition, added text for users who want to use protoc from the command line, with links to our protoc-gen-connect-web README.

View the docs here: https://connect.build/docs/web/generating-code#local-generation

Hopefully this makes things a bit more clear.