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

@akaoio/composer

v0.2.4

Published

Atomic document composition engine with real-time template processing

Readme

@akaoio/composer

A powerful, atomic documentation engine that builds comprehensive docs from small reusable content pieces. Self-documenting and production-ready for Node.js, Bun, Deno, and standalone server deployment.

✨ Features

Watch Mode

Automatic rebuilding when source files change, perfect for development workflows.

Template Engine

Built-in template engine with variable substitution supporting nested paths and array access.

Multi-Format Support

Seamlessly works with YAML, JSON, Markdown, HTML, and plain text files.

Flexible Build Pipeline

Configurable build tasks with custom processors for complex content transformations.

📦 Installation

Install via NPM

npm install @akaoio/composer

Install CLI Globally

npm install -g @akaoio/composer

Install via Deno

import { Composer } from "npm:@akaoio/composer@latest"

Install via Bun

bun add @akaoio/composer

🚀 Usage

Node.js Module Usage

const { Composer, BuildPipeline, ConfigLoader } = require('@akaoio/composer')

// Option 1: Simple usage
const composer = new Composer({
  dataPath: './data',
  templatesPath: './templates', 
  outputPath: './dist'
})

await composer.render()

// Option 2: Configuration-based
const loader = new ConfigLoader('./composer.config.js')
const config = await loader.loadConfig()
const pipeline = new BuildPipeline(config)
await pipeline.execute()

Deno Module Usage

import { Composer, BuildPipeline } from "npm:@akaoio/composer@latest"

// Deno with permissions
const composer = new Composer({
  dataPath: './data',
  templatesPath: './templates',
  outputPath: './dist'
})

await composer.render()

Run with permissions:

deno run --allow-read --allow-write --allow-env your-script.ts

Bun Module Usage

import { Composer, BuildPipeline, ConfigLoader } from '@akaoio/composer'

// Bun with TypeScript support
const composer = new Composer({
  dataPath: './data',
  templatesPath: './templates',
  outputPath: './dist'
})

await composer.render()

// Hot reload with Bun watch
import { watch } from 'fs'

composer.watch((outputs) => {
  console.log(`Rebuilt ${outputs.size} files`)
})

CLI Usage

# Initialize a new project
composer init

# Build documentation
composer build

# Watch for changes
composer watch

# Show help
composer help

🖥️ Server Deployment

Quick Start Server

# Clone and setup
git clone https://github.com/akaoio/composer.git
cd composer
npm install
npm run build

# Run as daemon service
npm run service:pm2

# Or with systemd
sudo npm run service:install

Docker Deployment

# Build image
docker build -f docker/Dockerfile.service -t composer-server .

# Run container
docker run -d \
  -p 3000:3000 \
  -v $(pwd)/data:/app/data \
  -v $(pwd)/output:/app/output \
  --name composer-server \
  composer-server

Health Monitoring

# Check service status
curl http://localhost:3000/health

# View build logs
curl http://localhost:3000/api/logs

# Trigger rebuild
curl -X POST http://localhost:3000/api/build

🤝 Contributing

Development Setup

Clone and Setup

git clone https://github.com/akaoio/composer.git
cd composer

# Install dependencies
npm install     # or `bun install` or `deno install`

# Build TypeScript
npm run build

# Run tests
npm test

# Build documentation (using composer itself!)
npm run build:doc

Development Principles

When contributing, follow these core principles:

  1. Class = Directory + Method-per-file - Every class is a directory
  2. Atomic Documentation - Each piece of content is a separate YAML file
  3. Test-Driven Development - Write tests first, implementation second
  4. 100% Real Implementation - No mocks, stubs, or placeholder code
  5. Zero Technical Debt - Complete every task fully before moving on
  6. Self-Documenting - This README is generated using Composer itself!

📄 License

MIT

🔗 Links

  • Repository: https://github.com/akaoio/composer
  • NPM Package: https://www.npmjs.com/package/@akaoio/composer
  • Documentation: Generated using Composer itself!

Generated with ❤️ by @akaoio/composer v0.2.3

This README demonstrates atomic documentation - every section is composed from individual YAML files in src/doc/readme/atom/