A Batteries-Included Backend Framework Levels Up
The AdonisJS v7 release marks a significant step forward for the “batteries-included” Node.js backend framework, sharpening its TypeScript-first positioning while simplifying setup for new and existing projects. Maintained by creator Harminder Virk, AdonisJS already targets teams that prefer a cohesive toolkit over assembling dozens of libraries. Version 7 builds on that philosophy with over 45 updated packages and three new ones, including @adonisjs/otel for OpenTelemetry integration, @adonisjs/content for typed content collections, and edge-markdown for rendering Markdown inside Edge templates. The framework continues to cover routing, the Lucid ORM, authentication, validation, mail, and templating under one umbrella, offering an opinionated alternative to ecosystems like NestJS and Laravel. For teams considering an upgrade from v6, the core team describes the transition as mostly mechanical, focused on renamed imports, configuration tweaks, and a refreshed encryption module, with a dedicated upgrade guide and GitHub discussion thread to smooth the path.
End-to-End Type Safety Through the Full Stack
End-to-end type safety is the headline feature of the AdonisJS v7 release, extending TypeScript guarantees from routing to API consumption. Route definitions now generate strongly typed helpers via urlFor, replacing the untyped router.makeUrl method from v6 and reducing fragile string-based URLs. A new transformer layer introduces a dedicated serialization mechanism that emits .d.ts declaration files at build time, letting frontend code rely on typed API response shapes without duplicating interfaces. In Inertia-powered applications, AdonisJS scans page components and enforces at compile time that inertia.render receives correct props, catching mismatches before they hit production. For separate frontend projects, a type-safe API client built on Tuyau carries these guarantees into TanStack Query or even plain fetch workflows. Together, these changes turn the framework into a TypeScript-first environment where server contracts and client usage stay aligned automatically.
Zero-Config OpenTelemetry Integration and Runtime Modernization
Observability becomes a first-class concern in AdonisJS v7 through zero-config OpenTelemetry integration. The new @adonisjs/otel package is wired directly into the framework, giving developers tracing and metrics out of the box instead of requiring separate instrumentation and configuration. This helps teams monitor performance, follow request flows, and investigate issues without bolting on additional monitoring stacks. Under the hood, v7 raises the minimum runtime to Node.js 24, allowing AdonisJS to lean on native platform APIs and reduce external dependencies. The dotenv library is replaced with Node’s built-in util.parseEnv, simplifying environment management. For development, an in-house JIT TypeScript runner called ts-exec, built on the Rust-based SWC compiler and weighing roughly 15 KB, replaces ts-node. These backend framework updates collectively aim to deliver faster startup, leaner tooling, and more insight into running applications with minimal configuration overhead.
Reworked Starter Kits and Developer Experience Improvements
AdonisJS v7 also revisits the onboarding experience with a set of reworked starter kits that favor clear, opinionated templates over interactive setup wizards. Instead of prompting developers through multiple configuration questions, the framework now offers four predefined kits—Hypermedia, API, React, and Vue—each bundling authentication flows, session management, and frontend tooling by default. This helps new teams standardize project structure more quickly and makes it easier to align on best practices. Barrel file generation for controllers, events, and policies further tidies codebases, replacing long walls of lazy imports at the top of route files with cleaner, centralized exports. Complementing these changes is a completely rebuilt documentation site designed to accelerate learning and reduce friction during upgrades. Community feedback has already highlighted the smooth migration path from v6, with the core team estimating most projects can move to v7 in under an hour.