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

Does Pulumi have an easy way to turn TS code into JS before passing it to a Cloudflare Worker?

That's not generally a Pulumi problem. That's a job for tsc or your preferred Typescript transpiler.

It's annoying to do the extra step manually or in CI.

All I want is a `NodejsFunction` equivalent from CDK.

Is this for deploying code to a remote runner? You have lambda-esque code that you want to transpile during deployment?

When you use wrangler and call `wrangler deploy`, it automatically does the transpilation and bundling.

But with Terraform (and thus Pulumi), you have to do it manually and then pass the output js file to the resource.

Sorry, I'm not being clear enough. Is this code that you want transpiled so that it can be run in the cloud, or is it Pulumi program code?

I used <https://registry.terraform.io/providers/jSherz/node-lambda-packager/latest|this provider> in the past, but I think Pulumi should solve this issue theirselves.

I know Pulumi has a Function Serializition thing for inline I think.

Then you should not try to do this during deployment. Just as you would not compile your C# or Java code during deployment. It may be possible, but you should not do it.

It does, and you should not use it. Just like you should not build your Docker image during deployment

Pulumi does allow this, and it's always breaks stuff for people.

What you are saying is nonsense. That's how CDK works. You run deploy and it uses esbuild behind the scene to do the job for you.

App-building and infra-deploying are very different, and should be strictly kept apart

From years of experience, it is always worse when you try this.

Yeah sure, I've been using it for 5 years and no issues.

Well I guess I can still use the Terraform provider to run esbuild. I hoped for a cleaner way tho.

Or need to use SST that uses Pulumi behind the scenes and handles the bundling for you.

It's dumb that you need a Pulumi wrapper to do the most basic stuff.

If all that TF provider is doing is calling esbuild you could probably just use the pulumi command provider instead, it will .tar up an output folder for you if needed:
<https://www.pulumi.com/registry/packages/command/api-docs/local/command/#archivepaths_nodejs>