AponiaJS vs AdonisJS

These two frameworks answer different questions. AdonisJS answers "how do I build a whole product"; AponiaJS answers "how do I organise an HTTP service on Bun".

At a glance

Routing is where they diverge first

AdonisJS keeps routes in a route file and points them at controller methods:

// start/routes.ts
import router from "@adonisjs/core/services/router";
const UsersController = () => import("#controllers/users_controller");

router.get("/users/:id", [UsersController, "show"]);

AponiaJS puts the path on the method:

import { Controller, Get, Param } from "@aponiajs/common";

@Controller("users")
export class UserController {
  @Get(":id")
  show(@Param("id") id: string) {
    return { id };
  }
}

Neither is better. A route file gives you one place to read the whole URL surface; decorators keep the path next to the code it runs. AponiaJS chose decorators because the module graph, not the router, is the organising idea — see controllers.

What AdonisJS gives you that you would have to build

Everything below is a first-party AdonisJS package and an unsolved problem in an AponiaJS application:

• Database. Lucid models, migrations, seeders, and relationships. In AponiaJS you register a client as a provider and inject it.
• Authentication and authorization. Guards and policies. In AponiaJS, authentication is an Elysia hook installed through native access, and there is no authorization primitive to attach a policy to.
• Configuration. Typed config files and validated environment variables. In AponiaJS, configuration is a value provider you wire yourself, usually with a dynamic module.
• Mail, queues, events, i18n, health checks, templating. No equivalents.

The corresponding AponiaJS argument is that you were going to choose those libraries anyway, and a smaller framework has less to disagree with. That is a real preference, not a technical advantage.

What AponiaJS gives you that AdonisJS does not

• Bun as the runtime, with Elysia's request handling rather than Node's HTTP server.
• End-to-end typed clients through Eden Treaty, inferred from the composed Elysia routes rather than generated from a spec. See Eden Treaty.
• Validator freedom. VineJS is the AdonisJS validator. AponiaJS accepts any Standard Schema validator, plus TypeBox and Elysia's t, described in validation.
• RFC 9457 Problem Details as the default error shape, in errors.

Which one to pick