AponiaJSDocs
Project

Status and roadmap

Implemented, experimental, and planned AponiaJS capabilities at the 0.6.0-alpha.18 source baseline.

Experimental software

AponiaJS 0.6.0-alpha.18 is an initial-development release. It is not recommended for production workloads, and its public API may change before 1.0.

Implemented

The current source implements:

  • decorated modules with imports, controllers, providers, and exports;
  • @Controller() and the GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS method decorators;
  • request parameter decorators for body, query, params, headers, cookies, the native request, response settings, and the whole context;
  • route validation through Standard Schema and platform-native validators across the body, query, params, headers, and response slots;
  • singleton class, value, factory, and alias providers;
  • class injection and explicit typed injection tokens;
  • module graph validation for cycles, duplicates, missing providers, invalid exports, and ambiguous providers;
  • managed AponiaFactory.create() and native AponiaFactory.createNative() bootstrap paths on the Elysia platform;
  • application handle, listen, getUrl, getNativeApplication, and close methods;
  • native Elysia configuration, module-imported Elysia plugins, and typed plugin context through ElysiaRouteContext;
  • statically composed native plugin and controller-descriptor route types for Eden Treaty;
  • bootstrap-compiled decorated route invokers, direct root registration, and explicit Elysia aot / precompile policy;
  • named validation-model classes through @Validation(), accepted in every route slot including cookie, with status-specific response maps;
  • HttpError, httpError, and httpErrors for RFC 9457 Problem Details responses on deliberately thrown application failures;
  • WebSocket gateways with provider registration, message, socket, server, and lifecycle decorators over the native Elysia and Bun socket runtime;
  • structured system logging, JSON logging, level filtering, and custom loggers;
  • project generation and the complete CLI file-schematic catalog, including REST resource validation models.

“Complete schematic catalog” describes generated file shapes. It does not mean every generated Nest-style capability is implemented by the runtime.

Not implemented

The runtime does not provide:

  • runtime guards, interceptors, middleware, or exception filters;
  • framework-owned mapping of native validation failures, or a serialization and unknown-field policy;
  • async providers or request and transient provider scopes;
  • lifecycle hooks or graceful drain coordination;
  • testing modules or provider overrides;
  • configuration, authentication, authorization, or rate-limiting packages;
  • OpenAPI generation or decorator-wide Eden Treaty inference;
  • a build-time module and route compiler;
  • GraphQL or microservice platforms, and the transport-neutral adapter SPI, handshake authentication, per-message schema policy, and connection limits that follow the WebSocket preview.

CLI output for these areas is scaffold-only.

Milestones

The source roadmap tracks 28 items across six milestones: 11 completed, 4 in progress, and 13 planned (47.50% overall):

MilestoneTargetStatus
Foundation alpha0.3.0Completed
Developer experience0.3.17Completed
Release quality0.5.0In progress
Runtime maturity0.7.0In progress
Production capabilities1.0.0Planned
Post-1.0 ecosystem1.1.0Planned

Active workstreams are foundation stabilization, dependency maintenance, native Elysia plugin type inference, and validation, errors, and serialization — the last at 45% after validation models and Problem Details errors landed. The Elysia WebSocket gateway preview is complete, which moves runtime maturity to 36.67% across six items. Static native route composition is implemented; decorator-wide inference remains part of the native-plugin workstream. Async lifecycle and provider scopes, the platform and HTTP package split, and full Elysia lifecycle conformance remain planned.

Use the source implementation and package exports as the authority for current behavior:

Benchmark status

The benchmark suite was removed from main at commit 61f9d69 during the 0.3.22 cycle, and the current source still contains no runnable benchmark command.

Previously published benchmark artifacts are historical snapshots. They depend on their Bun version, runner, workload, duration, and source revision and must not be presented as current production-capacity guarantees. Compare values only within the same published dataset.

See packages and versioning before installing a release.

On this page