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

I’ve had the same problems with configuring custom resources. I had some YAMLs to translate into pulumi (with TS), GitHub Copilot helped a bit. There were strange issues with some data types representation in the generated configurations, so I had to double-check everything when something wasn’t working as expected. But in general, it was quite reasonable to translate everything from YAML to pulumi as the configs became DRY.

according to opinionated TSconfig: I’ve found that it’s possible to disable the default TS (it uses too outdated TS version by default) in the root `Pulumi.yaml` :
```runtime:
  name: nodejs
  options:
    typescript: false```
Then compile your TS code as usual, and set the entrypoint for pulumi in `package.json` like this:
```"main": "dist/index.js",```


<@U05440H8RE3> the mentioned project hasn't been updated in a while because we rely on `crd2pulumi` also. At the moment, there are a number of issues to be fixed first.