Elysia on Next.js Node Runtime: Is the Node adapter necessary and how is the performance?

[shiqocred]

Hi everyone,

I am currently building a Next.js application and considering switching my API layer to ElysiaJS. However, I have a few concerns regarding the runtime and environment:

1. Node.js Runtime vs. Bun: Even though Elysia is optimized for Bun, I am required to use the Node.js runtime because my project relies on several Node-specific functions/built-in modules that are not yet fully covered or stable in Bun.

2. Using the Node Adapter: To run Elysia within Next.js Route Handlers on a Node environment, is it mandatory to use the @elysiajs/node adapter? Are there any significant limitations when running Elysia this way compared to its native Bun environment?

3. Performance Expectations: How does Elysia's performance hold up when running on Node.js via an adapter? Does it still offer a significant advantage over standard Next.js Route Handlers or Hono in a Node.js environment?

I’d love to hear from anyone who has benchmarked this or is running a similar stack in production.

Thanks!

[bismitpanda]

It is not an issue. You will not be using the adapter, you will be using it's WinterCG/WinterTC Web Standard compliance. So your first point will not matter as the runtime is still nodejs. You do not have to mention any adapter. I have not tested/tried the 3rd point. The only reason I use elysia is because of its eden treaty and openapi exports. I have to expose api so I am not using trpc/orpc.

I have used it in 3-4 applications and am still using it in new projects.

Check this: https://elysiajs.com/integrations/nextjs.html.
Goto https://elysiajs.com/quick-start.html and then select web standard. There you can see all the options you can use and why it works.