@navios/core 1.0.0-alpha.3 → 1.0.0

package/CHANGELOG.md

@@ -5,6 +5,69 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.0] - 2026-01-09
+
+### Added
+
+- **Stable Release**: First stable release of @navios/core
+  - Production-ready framework for building type-safe HTTP servers
+  - Comprehensive feature set with unified adapter architecture
+  - Full TypeScript support with end-to-end type safety
+
+## [1.0.0-alpha.4] - 2026-01-09
+
+### Added
+
+- **Unified Adapter Architecture**: New abstract adapter system supporting multiple adapter types (HTTP, CLI, etc.)
+  - `AbstractAdapterInterface` - Base interface for all adapters with lifecycle methods (`setupAdapter`, `onModulesInit`, `ready`, `dispose`)
+  - `AdapterEnvironment` - Base interface for adapter environments with type-safe options
+  - `HttpAdapterEnvironment` - Extended environment interface for HTTP adapters with server, CORS, multipart, and listen options types
+  - `DefaultAdapterEnvironment` - Default environment with unknown types for generic usage
+  - `AdapterToken` - New injection token for accessing the current adapter instance
+  - `AdapterFactory` - Factory for creating adapter instances from environment definitions
+- **Type-Safe Application Generic**: `NaviosApplication<TEnvironment>` now accepts an environment type parameter
+  - All adapter-specific methods (`configure`, `enableCors`, `enableMultipart`, `listen`, `getServer`) are now properly typed based on the environment
+  - Environment types provide IntelliSense for adapter-specific options
+- **Enhanced Plugin System**: Plugins are now typed with adapter constraints
+  - `NaviosPlugin<TOptions, TAdapter>` - Second type parameter for adapter-specific plugins
+  - `PluginContext<TAdapter>` - Typed context with adapter access
+  - Plugins can access `context.adapter` instead of `context.server` for better type safety
+- **Module Custom Entries**: New `customEntries` property on `ModuleMetadata` for adapter-specific module data
+  - Allows adapters to store custom metadata on modules (e.g., commands for CLI adapter)
+- **Console Logger Tests**: Added comprehensive test suite for `ConsoleLoggerService`
+
+### Changed
+
+- **Renamed Environment Methods**: `getHttpToken` renamed to `getToken` for adapter-agnostic naming
+- **Renamed Environment Property**: `httpTokens` renamed to `tokens` in environment definitions
+- **Application Configuration**: New `configure()` method replaces `setupHttpServer()` for pre-init configuration
+  - Configuration options are merged with adapter defaults
+  - Must be called before `init()` for options to take effect
+- **Plugin Context**: `PluginContext.server` replaced with `PluginContext.adapter` for accessing the adapter instance
+  - Use `context.adapter.getServer()` for HTTP server access
+  - `context.globalPrefix` removed; use `context.adapter.getGlobalPrefix()` instead
+- **Abstract HTTP Adapter**: `AbstractHttpAdapterInterface` now extends `AbstractAdapterInterface`
+  - Added `configure(options)` method for pre-init configuration
+  - Method signatures updated for environment-based typing
+
+### Breaking Changes
+
+- **Environment Definition Format**: `httpTokens` property renamed to `tokens`
+  - Before: `{ httpTokens: new Map([...]) }`
+  - After: `{ tokens: new Map([...]) }`
+- **Plugin Context API**: `context.server` and `context.globalPrefix` removed
+  - Before: `const server = context.server`
+  - After: `const server = context.adapter.getServer()`
+  - Before: `const prefix = context.globalPrefix`
+  - After: `const prefix = context.adapter.getGlobalPrefix()`
+- **Application Setup**: `setupHttpServer()` replaced with `configure()`
+  - Before: `await app.setupHttpServer({ logger: true })`
+  - After: `app.configure({ logger: true }); await app.init()`
+
+### Dependencies
+
+- Updated to support unified adapter architecture across all packages
+
 ## [1.0.0-alpha.3] - 2026-01-08
 
 ### Added

package/README.md

@@ -169,14 +169,14 @@ Create your first Controller:
 ```ts
 import type { EndpointParams } from '@navios/core'
 
-import { Controller, Endpoint, syncInject } from '@navios/core'
+import { Controller, Endpoint, inject } from '@navios/core'
 
 import { AuthService } from './auth.service.mjs'
 
 @Controller()
 export class AuthController {
   // Inject the LoginService
-  loginService = syncInject(LoginService)
+  loginService = inject(LoginService)
 
   @Endpoint(login)
   async login(request: EndpointParams<typeof login>) {

package/docs/legacy-compat.md

@@ -21,7 +21,16 @@ No additional installation is required. The legacy-compat decorators are include
 To use legacy-compatible decorators, import them from the `legacy-compat` subpath:
 
 ```typescript
-import { Module, Controller, Endpoint, UseGuards, Header, HttpCode, Multipart, Stream } from '@navios/core/legacy-compat'
+import {
+  Controller,
+  Endpoint,
+  Header,
+  HttpCode,
+  Module,
+  Multipart,
+  Stream,
+  UseGuards,
+} from '@navios/core/legacy-compat'
 ```
 
 ## Available Decorators
@@ -65,12 +74,16 @@ export class UserController {
 Defines an HTTP endpoint with type-safe request/response schemas. Must be applied to methods.
 
 ```typescript
-import { Controller, Endpoint, type EndpointParams, type EndpointResult } from '@navios/core/legacy-compat'
+import type { EndpointParams, EndpointResult } from '@navios/core/legacy-compat'
+
+import { Controller, Endpoint } from '@navios/core/legacy-compat'
 
 @Controller()
 export class UserController {
   @Endpoint(getUserEndpoint)
-  async getUser(request: EndpointParams<typeof getUserEndpoint>): Promise<EndpointResult<typeof getUserEndpoint>> {
+  async getUser(
+    request: EndpointParams<typeof getUserEndpoint>,
+  ): Promise<EndpointResult<typeof getUserEndpoint>> {
     const { id } = request
     return { id, name: 'John Doe' }
   }
@@ -82,12 +95,19 @@ export class UserController {
 Defines a multipart/form-data endpoint for file uploads. Must be applied to methods.
 
 ```typescript
-import { Controller, Multipart, type MultipartParams, type MultipartResult } from '@navios/core/legacy-compat'
+import type {
+  MultipartParams,
+  MultipartResult,
+} from '@navios/core/legacy-compat'
+
+import { Controller, Multipart } from '@navios/core/legacy-compat'
 
 @Controller()
 export class FileController {
   @Multipart(uploadFileEndpoint)
-  async uploadFile(request: MultipartParams<typeof uploadFileEndpoint>): Promise<MultipartResult<typeof uploadFileEndpoint>> {
+  async uploadFile(
+    request: MultipartParams<typeof uploadFileEndpoint>,
+  ): Promise<MultipartResult<typeof uploadFileEndpoint>> {
     const { file } = request.data
     return { url: 'https://example.com/file.jpg' }
   }
@@ -99,12 +119,17 @@ export class FileController {
 Defines a streaming endpoint. Must be applied to methods.
 
 ```typescript
-import { Controller, Stream, type StreamParams } from '@navios/core/legacy-compat'
+import type { StreamParams } from '@navios/core/legacy-compat'
+
+import { Controller, Stream } from '@navios/core/legacy-compat'
 
 @Controller()
 export class FileController {
   @Stream(downloadFileEndpoint)
-  async downloadFile(request: StreamParams<typeof downloadFileEndpoint>, reply: any): Promise<void> {
+  async downloadFile(
+    request: StreamParams<typeof downloadFileEndpoint>,
+    reply: any,
+  ): Promise<void> {
     const { fileId } = request.urlParams
     // Stream file data to reply
   }
@@ -176,10 +201,10 @@ The legacy-compat module also exports type utilities for working with endpoints:
 
 ```typescript
 import type {
-  ModuleOptions,
   ControllerOptions,
   EndpointParams,
   EndpointResult,
+  ModuleOptions,
   MultipartParams,
   MultipartResult,
   StreamParams,
@@ -191,9 +216,18 @@ import type {
 Here's a complete example using legacy-compatible decorators:
 
 ```typescript
+import type { EndpointParams, EndpointResult } from '@navios/core/legacy-compat'
+
 import { builder } from '@navios/builder'
-import { Module, Controller, Endpoint, UseGuards, HttpCode, type EndpointParams, type EndpointResult } from '@navios/core/legacy-compat'
-import { Injectable, syncInject } from '@navios/core'
+import { inject, Injectable } from '@navios/core'
+import {
+  Controller,
+  Endpoint,
+  HttpCode,
+  Module,
+  UseGuards,
+} from '@navios/core/legacy-compat'
+
 import { z } from 'zod/v4'
 
 // Define API endpoints
@@ -239,17 +273,21 @@ export class UserService {
 @Controller()
 @UseGuards(AuthGuard)
 export class UserController {
-  userService = syncInject(UserService)
+  userService = inject(UserService)
 
   @Endpoint(getUserEndpoint)
-  async getUser(request: EndpointParams<typeof getUserEndpoint>): Promise<EndpointResult<typeof getUserEndpoint>> {
+  async getUser(
+    request: EndpointParams<typeof getUserEndpoint>,
+  ): Promise<EndpointResult<typeof getUserEndpoint>> {
     const { id } = request.urlParams
     return await this.userService.findById(id)
   }
 
   @Endpoint(createUserEndpoint)
   @HttpCode(201)
-  async createUser(request: EndpointParams<typeof createUserEndpoint>): Promise<EndpointResult<typeof createUserEndpoint>> {
+  async createUser(
+    request: EndpointParams<typeof createUserEndpoint>,
+  ): Promise<EndpointResult<typeof createUserEndpoint>> {
     const { name, email } = request.body
     return await this.userService.create({ name, email })
   }
@@ -270,10 +308,9 @@ If you're migrating from standard decorators to legacy-compatible decorators:
 
 ```typescript
 // Before
-import { Module, Controller, Endpoint } from '@navios/core'
-
+import { Controller, Endpoint, Module } from '@navios/core'
 // After
-import { Module, Controller, Endpoint } from '@navios/core/legacy-compat'
+import { Controller, Endpoint, Module } from '@navios/core/legacy-compat'
 ```
 
 2. Ensure your `tsconfig.json` has `experimentalDecorators` enabled:
@@ -317,4 +354,3 @@ The `emitDecoratorMetadata` option is optional but recommended for better runtim
 - Legacy-compatible decorators are fully compatible with all Navios features including guards, attributes, dependency injection, and adapters
 - You can mix legacy-compatible decorators with standard decorators in the same project, but it's recommended to use one approach consistently
 - The legacy-compat module is maintained alongside the standard decorators and receives the same updates and bug fixes
-

package/docs/quick-start.md

@@ -117,19 +117,14 @@ Create a user controller (`controllers/user.controller.ts`):
 ```ts
 import type { EndpointParams } from '@navios/core'
 
-import {
-  Controller,
-  Endpoint,
-  NotFoundException,
-  syncInject,
-} from '@navios/core'
+import { Controller, Endpoint, inject, NotFoundException } from '@navios/core'
 
 import { createUserEndpoint, getUserEndpoint } from '../api/index.js'
 import { UserService } from '../services/user.service.js'
 
 @Controller()
 export class UserController {
-  private userService = syncInject(UserService)
+  private userService = inject(UserService)
 
   @Endpoint(createUserEndpoint)
   async createUser(request: EndpointParams<typeof createUserEndpoint>) {