aws-cdk

I've been using Bun since 2022 just to be trendy for recruitment (it worked, and still works despite it almost being 2026) Bun is fast, and its worked as a drop in replacement for npm in large legacy projects too. I only ever encountered one issue, which was pretty dumb, Amazon's CDK has hardcoded references to various package manager's lock files, and Bun wasn't one of them https://github.com/aws/aws-cdk/issues/31753 This wasn't fixed till the end of 2024 and as you can see, only accidentally merged in but tolerated. It was promptly broken by a bun breaking change https://github.com/aws/aws-cdk/issues/33464 but don't let Amazon's own incompetency be the confirmation bias you were looking for about using a different package manager in production you can use SST to deploy cloud resources on AWS and any cloud, and that package works with bu

I'm quite happy with CDK[0]. My experience is only with the main AWS cloudformation based version of CDK, although there is also CDK for terraform, which supports any resource that terraform supports, although some of what I'm about to say is not applicable to that version. What I like about CDK, is that you can write real code, and it supports a wide range of languages, although typescript is the best experience. Provided that you don't use any of the `fromLookup` type functions, you can run and test the code without needing any actual credentials to your cloud provider. CDK essentially complies your code into a cloudformation template, you can run the build without credentials, then deploy the built cloudformation template separately. You don't need to worry about your terraform server crashing half way though a deployment, because clou