Changelog - 2026-10-17

A generated artifact index for the application

New Feature

In one line. An application returns the index ignis-artifacts generate emits from artifacts(), the same file an IGNIS backend passes to createAppConfig.

import { BaseArdorApplication, type IApplicationInfo, type IArtifactIndex } from '@venizia/ardor';

const GeneratedArtifacts: IArtifactIndex = { services: [] }; // from src/_artifacts.ts

class Application extends BaseArdorApplication {
  getAppInfo(): IApplicationInfo {
    return { name: 'shop', version: '1.0.0', description: 'Shop admin' };
  }

  override artifacts(): Array<IArtifactIndex> {
    return [GeneratedArtifacts];
  }

  bindContext(): void {}
}

What changed

• artifacts() on the application. It returns Array<IArtifactIndex> and defaults to []. An index holds each stereotyped class by value, so a bundler keeps the module instead of dropping a side-effect import.
• start() checks the index. It throws [artifacts] '<kind>' lists <Class>, which was never discovered when a listed class has no stereotype or the index is stale.
• An IGNIS artifact group is accepted. start() checks the flat index a group carries as content. A group without content is resolved first: start() awaits its resolve() and checks the index it returns. A group with neither content nor a resolve function makes start() throw, naming AutoArtifacts and IgnisArtifactsPlugin.
• @venizia/ignis-boot/auto registers the application's decorated classes. @venizia/ignis-boot 0.2.1-1 adds AutoArtifacts and IgnisArtifactsPlugin. Return AutoArtifacts from artifacts(): bun run resolves it in start(), and Bun.build with the plugin gives the bundle its class list, so it carries no scanner: a server build resolves it through a resolve(), a browser build imports it eagerly as content. In a browser build, import the auto module from the application's own module, not from a shared kit. A class that loses its decorator is simply not registered.
• IArtifactIndex is exported from @venizia/ardor and @venizia/ardor-kernel. It has the six fields the generator emits, configurations to controllers.

Who is affected

• An application that imports a hand-written register-artifacts file. Nothing breaks. To move to the shared generator, install @venizia/ignis-boot 0.2.1-1, run ignis-artifacts generate --root src --out src/_artifacts.ts --source-module @venizia/ardor and return its export from artifacts().
• Everyone else. No action needed. Discovery binds the same classes as before.