Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Currently, AdonisJS v7 is primarily designed and tested for Node.js. While some developers have successfully run AdonisJS on Bun with workarounds, there is no official support or guarantees.

Many developers are migrating to Bun because of its significantly faster startup time, better performance, and modern developer experience. It would be great if AdonisJS could officially support Bun as a first-class runtime.

  • Official compatibility with Bun as a runtime.
  • Update documentation to include Bun installation and usage instructions.
  • Ensure core packages (@adonisjs/core, @adonisjs/lucid, @adonisjs/auth, etc.) work properly under Bun without major workarounds.
  • Add Bun to the CI matrix for testing (optional but appreciated).
  • Provide a recommended way to run ace commands and the development server using Bun.

Additional context

Bun is gaining a lot of traction in the TypeScript ecosystem. Adding official support would make AdonisJS more attractive to developers who prefer Bun over Node.js, similar to how frameworks like Elysia, Hono, and NestJS are embracing Bun.

Related packages that might need attention:

  • @adonisjs/core
  • @adonisjs/lucid / database drivers
  • @adonisjs/assembler
  • File system and process-related utilities

Would the AdonisJS team be open to exploring official Bun support?

You must be logged in to vote

Replies: 1 comment

Comment options

Appreciate the writeup.

  1. I'm low on bandwidth as the primary maintainer, so I can't actively drive Bun support myself. I'd rather be upfront about that than half-commit.

  2. That said, I'm not closed to it. If someone wants to champion Bun compatibility I'd happily plan a roadmap around it. To set expectations: "champion" here means running the test suites for @adonisjs/core, @adonisjs/lucid, and @adonisjs/assembler under Bun, filing concrete failures (most should become Bun-side bugs, not AdonisJS changes), and being around long enough to maintain a Bun CI lane and the docs page that goes with it. That's the level of sustained involvement that would unlock official support.

  3. Worth noting that Bun's own positioning is drop-in Node.js compatibility, and that's still their roadmap as far as I know. So in most cases this isn't about adding Bun-specific code to AdonisJS. It's about validating what already works, surfacing what doesn't, and pushing those gaps upstream.

If anyone here is interested in taking point on (1) and (2), reply on this thread and we'll figure out the next step.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
💡
Ideas
Labels
None yet
2 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.