This message was deleted.

TypeScript has been a wonderful experience for our team. We catch code issues earlier, even if it's not doing runtime typing, the transplied javascript is more reliable than just javascript, even if you have 100% test coverage.

typescript works well when you have defined interface types, especially for external APIs

Pulumi provides its own interpreter for typescript, so you don't need to install typescript as a dependencies. You can continue to write your applications in javascript, but you're missing out.

Also typescript in Pulumi does not imply typescript in the lambdas that Pulumi deploys. Separate code.

@little-cartoon-10569 Ahhh that’s a good one! Do you have any links that explain how this can be achieved? Thanks 🙂

The Pulumi

index.ts

declares your resources, and with some magic functions, it can also package up your apps to deploy to those resources. Your build process doesn't have to be coupled with Pulumi, or even exist. Javascript doesn't need to be "built" assuming you don't have dependencies, but even if you did, it's about telling the Pulumi plan where your artifacts that get deployed to your resources are. Examples: • https://github.com/pulumi/examples/tree/master/aws-ts-lambda-thumbnailer (js in a docker runtime for lambda) • https://github.com/pulumi/examples/tree/master/aws-ts-voting-app (python app to ecs) • https://github.com/pulumi/examples/blob/master/aws-ts-apigateway/index.ts#L23-L49 (js in lambda via Pulumi magic)