No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi all, could there be an issue with the latest release of Pulumi where it makes plugins running in child process believe they should print color output? I am seeing this error since v3.70 where it looks like `@grpc/grpc-js` is correctly printing the port, but unfortunately it's being wrapped in ANSI color codes...

```pulumi:providers:pulumi-nodejs default  error: pulumi-nodejs (resource) plugin [/opt/homebrew/bin/pulumi-resource-pulumi-nodejs] wrote a non-numeric port to stdout ('0'): strconv.Atoi: parsing "\x1b[33m65010\x1b[39m": invalid syntax```

Has someone gotten back to you on this or did you file a GitHub issue? This is pretty surprising

Hi friel :slightly_smiling_face: I raised this issue on github: <https://github.com/pulumi/pulumi/issues/13150>

I have a sneaking feeling this may be due to node v20.3 which I've also noticed has caused problems with other libraries as well, e.g. esbuild.

For now I'm just manually editing `node_modules/@pulumi/pulumi/cmd/dynamic-provider/index.js` and wrapping port in a String, e.g. `console.log(String(port));`