What is the motivation / use case for changing the behavior?
The improved performance, and fast adoption of Bun is a testament to the value it brings.
As the JS ecosystem is further fragmented between Node, Deno and Bun, supporting Bun would at least allow users the option of still using NestJS.
The apparent interop between Node and Bun, unlike Deno, makes this new runtime an appealing prospect for users looking for improved performance, and native TypeScript support, amongst other things.
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
The ability to make use of more JS runtimes, in particular, Bun: https://bun.sh/
Describe the solution you'd like
Now that Bun has been released, I'm sure I'm not the only one that would like to make use of it, and all of the benefits it brings.
Faster runtime, no more TypeScript transpilation, etc.
From what I can tell, the interop between Node and Bun is good, but this will probably involve an unknown amount of work.
It would be really appealing for users of NestJS to be able to choose between these runtimes.
Teachability, documentation, adoption, migration strategy
https://bun.sh/
What is the motivation / use case for changing the behavior?
The improved performance, and fast adoption of Bun is a testament to the value it brings.
As the JS ecosystem is further fragmented between Node, Deno and Bun, supporting Bun would at least allow users the option of still using NestJS.
The apparent interop between Node and Bun, unlike Deno, makes this new runtime an appealing prospect for users looking for improved performance, and native TypeScript support, amongst other things.