When Pulumi makes Bun a fully supported runtime, it's not just adding another checkbox to a compatibility list. It's a quiet acknowledgment that the JavaScript ecosystem's center of gravity has shifted, and infrastructure tooling should follow the developer, not the other way around. For too long, running infrastructure as code meant accepting Node.js as a non-negotiable prerequisite, even when your application code had already moved on. With Pulumi 3.227.0, that friction disappears: set `runtime: bun` in your `Pulumi.yaml`, and Bun handles the entire program execution. No Node.js installation, no version manager dance, no hidden dependency lurking in CI.
The practical impact here is straightforward for teams already using Bun in their application layer. You now have one less runtime to install, patch, and reason about across your pipelines. That might sound modest, but infrastructure management is often a game of accumulated overhead. Every extra tool in the chain is a place where versions drift, security advisories pile up, and debugging sessions go to die. By letting Bun own both your application runtime and your infrastructure runtime, Pulumi removes a whole class of environment mismatch issues. The same runtime that runs your code is now the one that provisions your cloud resources. That consistency is not a luxury; it's the kind of simplification that saves real hours on real Tuesday afternoons.
What makes this notable is not that Bun is faster or newer, though it is both. It's that Pulumi is signaling a willingness to meet users where they actually are, not where legacy assumptions say they should be. The announcement doesn't disparage Node.js or force a migration. It simply opens the door for teams that have already standardized on Bun to bring that preference into their infrastructure workflows without a second-class experience. This is the kind of incremental, practical progress that moves the industry forward: not a dramatic rewrite, but a deliberate removal of a barrier that used to feel permanent.
If you're evaluating this for your own team, the question is not whether Bun is better than Node.js in the abstract. It's whether your infrastructure code should depend on a runtime you no longer use anywhere else. For many teams, the answer is no. And now, with Pulumi's support, that answer no longer forces you to stay stuck. The path is simple: update your `Pulumi.yaml`, point it at Bun, and let your infrastructure run the same way your applications already do. That's not a headline. It's just a better way to work.