sparse-intern-71089
02/07/2022, 4:26 PMmillions-furniture-75402
02/07/2022, 4:47 PMmammoth-art-6111
02/07/2022, 5:09 PMmammoth-art-6111
02/07/2022, 5:10 PMmammoth-art-6111
02/07/2022, 5:21 PMmillions-furniture-75402
02/07/2022, 6:08 PMlittle-cartoon-10569
02/07/2022, 8:18 PMrough-intern-34947
02/08/2022, 10:55 AMmillions-furniture-75402
02/08/2022, 3:11 PMindex.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)