npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@macss/modular-api

v0.6.1

Published

Use-case-centric toolkit for building modular APIs with Express. Define UseCase classes (input → validate → execute → output), connect them to HTTP routes, and expose Swagger/OpenAPI documentation automatically.

Downloads

423

Readme

modular-api

Use-case centric toolkit for building modular APIs with Express.
Define UseCase classes (input → validate → execute → output), connect them to HTTP routes, and get automatic Swagger/OpenAPI documentation.

Also available in Dart: modular_api · Python: macss-modular-api


Quick start

import { ModularApi, ModuleBuilder } from '@macss/modular-api';

// ─── Module builder (separate file in real projects) ──────────
function buildGreetingsModule(m: ModuleBuilder): void {
  m.usecase('hello', HelloWorld.fromJson);
}

// ─── Server ───────────────────────────────────────────────────
const api = new ModularApi({ basePath: '/api' });

api.module('greetings', buildGreetingsModule);

api.serve({ port: 8080 });
curl -X POST http://localhost:8080/api/greetings/hello \
  -H "Content-Type: application/json" \
  -d '{"name":"World"}'
{ "message": "Hello, World!" }

Docshttp://localhost:8080/api/docs Healthhttp://localhost:8080/api/health OpenAPI JSONhttp://localhost:8080/api/openapi.json (also /api/openapi.yaml) Metricshttp://localhost:8080/api/metrics (opt-in)

See example/example.ts for the full implementation including Input, Output, UseCase with validate(), and the builder.


Features

  • UseCase<I, O> — pure business logic, no HTTP concerns
  • Input / Output — DTOs with automatic OpenAPI schema generation via @Field decorators
  • Output.statusCode — custom HTTP status codes per response
  • UseCaseException — structured error handling (status code, message, error code, details)
  • ModularApi + ModuleBuilder — module registration and routing
  • Constructor-based unit testing with fake dependency injection
  • cors() middleware — built-in CORS support
  • All public endpoints resolve under the configured basePath.
  • Swagger UI at /{basePath}/docs — auto-generated from registered use cases
  • OpenAPI spec at /{basePath}/openapi.json and /{basePath}/openapi.yaml — raw spec download
  • Health check at GET /{basePath}/healthIETF Health Check Response Format
  • Prometheus metrics at GET /{basePath}/metricsPrometheus exposition format
  • Structured JSON logging — Loki/Grafana compatible, request-scoped with trace_id
  • All endpoints default to POST (configurable per use case)
  • Full TypeScript declarations (.d.ts) included

Plugin host

The public plugin contract is available from the package exports and is already used by the official health, metrics, OpenAPI, and docs plugins.

Current lifecycle behavior:

  • api.plugin(...) registers a plugin instance without running setup yet
  • setup(host) runs during serve() in dependency order
  • validate(host) runs after registration freeze and can abort startup
  • shutdown() runs in reverse setup order on normal shutdown and on partial startup rollback
  • plugin routes always resolve under the configured basePath
  • all three public middleware slots are active with deterministic ordering
import {
  ModularApi,
  type Plugin,
  type PluginHost,
  type PluginManifest,
} from '@macss/modular-api';

class HelloPlugin implements Plugin {
  readonly manifest: PluginManifest = {
    id: 'acme.hello',
    displayName: 'Hello Plugin',
    version: '0.1.0',
    hostApiVersion: '>=0.1.0 <0.2.0',
  };

  setup(host: PluginHost): void {
    host.registerRoute({
      id: 'hello-plugin',
      method: 'GET',
      path: '/hello-plugin',
      visibility: 'custom',
      // Optional OpenAPI Operation object — when present, the official
      // OpenApiPlugin merges the route into /openapi.json and /docs (ADR-0003).
      openapi: {
        summary: 'Hello from a plugin route',
        responses: { '200': { description: 'OK' } },
      },
      handler: () => ({
        status: 200,
        body: { ok: true, basePath: host.metadata().basePath },
      }),
    });
  }

  validate() {
    return [];
  }
}

const api = new ModularApi({ basePath: '/api' }).plugin(new HelloPlugin());
await api.serve({ port: 8080 });

Installation

npm install @macss/modular-api

If you use SqlServerMetadataReader for SQL Server introspection, install mssql explicitly:

npm install @macss/modular-api mssql

Error handling

async execute() {
  const user = await repository.findById(this.input.userId);
  if (!user) {
    throw new UseCaseException({
      statusCode: 404,
      message: 'User not found',
      errorCode: 'USER_NOT_FOUND',
    });
  }
  return new GetUserOutput(user);
}
{ "error": "USER_NOT_FOUND", "message": "User not found" }

Testing

Write true unit tests by injecting fake dependencies directly through the constructor. No HTTP server or real infrastructure needed.

import { describe, it, expect, beforeEach } from 'vitest';
import { UseCaseException } from '@macss/modular-api';

// ─── Fake ────────────────────────────────────────────────────
class FakeGreetingRepository implements GreetingRepository {
  saved: string[] = [];

  async save(name: string): Promise<void> {
    this.saved.push(name);
  }
}

// ─── Tests ───────────────────────────────────────────────────
describe('SayHello', () => {
  let fakeRepo: FakeGreetingRepository;

  beforeEach(() => {
    fakeRepo = new FakeGreetingRepository();
  });

  it('greets correctly', async () => {
    const usecase = new SayHello(new SayHelloInput('World'), { repository: fakeRepo });

    expect(usecase.validate()).toBeNull();

    const output = await usecase.execute();

    expect(output.message).toBe('Hello, World!');
    expect(fakeRepo.saved).toContain('World');
  });

  it('rejects empty name', () => {
    const usecase = new SayHello(new SayHelloInput(''), { repository: fakeRepo });

    expect(usecase.validate()).not.toBeNull();
  });

  it('throws UseCaseException when repo fails', async () => {
    const failingRepo = {
      save: async () => {
        throw new Error('DB error');
      },
    };

    const usecase = new SayHello(new SayHelloInput('World'), { repository: failingRepo });

    await expect(usecase.execute()).rejects.toThrow(UseCaseException);
  });
});

For integration tests against real infrastructure, use UseCase.fromJson() directly (no helper wrapper needed):

it('integration — end to end with real DB', async () => {
  const usecase = SayHello.fromJson({ name: 'World' });
  const output = await usecase.execute();
  expect(output.message).toBe('Hello, World!');
});

See doc/testing_guide.md for the full guide.


Architecture

HTTP Request → ModularApi → Module → UseCase → Business Logic → Output → HTTP Response
  • UseCase layer — pure logic, independent of HTTP
  • HTTP adapter — turns a UseCase into an Express RequestHandler
  • Middlewares — cross-cutting concerns (CORS, logging)
  • Swagger UI — documentation served automatically

License

MIT © ccisne.dev