News for hackers. Stuff that matters.

A comment on Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue. Parent comment

Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea... by yieldcrv on Wednesday November 06, 2024 @09:13PM (#42072570)
Cant use bun to deploy CDK, CDK fails as it looks for package-lock yarn-lock or pnpm’s exclusively

So dumb. Trying to move to SST for only that reason

but if you add cdk to the path, you can still deploy, its just that your cicd and deployment scripts are not all using bun anymore

[ Parent | on HN ]
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea... by hinkley on Thursday November 07, 2024 @12:11AM (#42073608)
mmm, I wonder how hard that would be to fix in a PR.
[ Parent | on HN ]
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea... by yieldcrv on Thursday November 07, 2024 @12:14AM (#42073617)
actually good idea, didnt think about it
[ Parent | on HN ]
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea... by Tehnix on Thursday November 07, 2024 @05:56AM (#42075563)
Hmm, beyond a bug they had in bun between version 1.0.8 and 1.1.20[0] bun has otherwise worked perfectly fine for me

You have to do a few adjustments which you can see here https://github.com/codetalkio/bun-issue-cdk-repro?tab=readme...

- Change app/cdk.json to use bun instead of ts-node

- Remove package-lock.json + existing node_modules and run bun install

- You can now use bun run cdk as normal

[0]: https://github.com/codetalkio/bun-issue-cdk-repro

[ Parent | on HN ]