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

laikacms

v1.0.1

Published

The basis for modern content management.

Readme

laikacms

Modular, runtime-agnostic content management. The basis for modern CMS apps.

API-first headless CMS designed to work with Decap CMS or your own UI. Swap storage backends (filesystem, R2, GitHub, …) without rewriting code. Runs on Node, Bun, and Cloudflare Workers.

pnpm add laikacms

Quick start

Node / Bun

import { buildJsonApi } from 'laikacms/storage-api';
import { FileSystemStorageRepository } from 'laikacms/storage-fs';
import { markdownSerializer } from 'laikacms/storage-serializers-markdown';

const repo = new FileSystemStorageRepository('./content', { md: markdownSerializer }, 'md');
const api = buildJsonApi({ repo });

export default { fetch: api.fetch };

Cloudflare Workers

import { buildJsonApi } from 'laikacms/storage-api';
import { R2StorageRepository } from 'laikacms/storage-r2';
import { markdownSerializer } from 'laikacms/storage-serializers-markdown';

export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const repo = new R2StorageRepository(env.CONTENT_BUCKET, { md: markdownSerializer }, 'md');
    return buildJsonApi({ repo }).fetch(request);
  },
};

What's in the box

laikacms is a single package with many focused subpath exports. Import only what you need.

APIs (JSON:API HTTP layer)

| Export | Purpose | | -------------------------- | ---------------------------------- | | laikacms/storage-api | Storage CRUD over JSON:API | | laikacms/documents-api | Document/record CRUD over JSON:API | | laikacms/assets-api | Asset metadata + uploads | | laikacms/contentbase-api | Contentbase settings management |

Domain (interfaces & entities)

| Export | Purpose | | ------------------------------- | ------------------------------- | | laikacms/storage | StorageRepository interface | | laikacms/documents | DocumentsRepository interface | | laikacms/assets | AssetsRepository interface | | laikacms/contentbase-settings | SettingsProvider interface |

Implementations

| Export | Backs | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | laikacms/storage-fs | Filesystem | | laikacms/storage-r2 | Cloudflare R2 | | laikacms/storage-s3 | S3→R2Bucket adapter (createS3Bucket()) — use with R2StorageRepository; not a StorageRepository itself. Full S3 StorageRepository: @laikacms/aws/storage-s3 | | laikacms/storage-webdav | WebDAV server | | laikacms/storage-drizzle | SQL via Drizzle | | laikacms/storage-jsonapi-proxy | Remote JSON:API server | | laikacms/documents-contentbase | Documents on top of storage | | laikacms/documents-drizzle | Documents in SQL | | laikacms/documents-jsonapi-proxy | Documents via JSON:API proxy | | laikacms/documents-obsidian | Obsidian-vault-backed documents | | laikacms/assets-contentbase | Assets on top of storage | | laikacms/assets-r2 | Assets in R2 | | laikacms/assets-jsonapi-proxy | Assets via JSON:API proxy | | laikacms/assets-obsidian | Obsidian-vault-backed assets — Node.js / Bun only (uses node:fs / node:path / node:stream; not available on Cloudflare Workers) | | laikacms/contentbase-settings-default | In-memory / file-backed settings | | laikacms/contentbase-settings-decap | Decap-CMS-compatible settings |

Testing utilities

| Export | Purpose | | ---------------------------- | --------------------------------------------------------------- | | laikacms/documents/testing | Contract test harness for DocumentsRepository implementations | | laikacms/storage/testing | Contract test harness for StorageRepository implementations | | laikacms/assets/testing | Contract test harness for AssetsRepository implementations |

Serializers

laikacms/storage-serializers-json · …-yaml · …-markdown · …-raw

Shared utilities

laikacms/core · laikacms/crypto · laikacms/file-sanitizer · laikacms/sanitizer · laikacms/json-api · laikacms/i18n (/en, /nl)

Companion packages

Documentation

Full docs, architecture notes, and deployment guides live in the laikacms repository.

Compat helpers — Promise-friendly entry points

laikacms/compat exports two Promise-friendly wrappers for non-Effect consumers:

  • runTask(task, options?) — runs a LaikaTask and resolves with its value.
  • collectStream(stream, options?) — drains a LaikaStream and resolves with { items, done }.

Both accept an optional onProgress callback that is called for every LaikaMetadata event — both Progress and RecoverableError — as the task/stream runs.

import { collectStream, runTask } from 'laikacms/compat';

// Task — receive progress events without importing Effect
const result = await runTask(myTask, {
  onProgress(meta) {
    if (meta._tag === 'Progress') console.log(meta.progress.message);
    if (meta._tag === 'RecoverableError') console.warn(meta.error);
  },
});

// Stream — metadata fires live; data is still collected into items
const { items, done } = await collectStream(myStream, {
  onProgress(meta) {
    if (meta._tag === 'Progress') updateProgressBar(meta.progress);
  },
});

Omitting options (or onProgress) uses a data-only fast path. Note that when onProgress is omitted, RecoverableError and Progress events are silently discarded — callers that need to surface warnings or non-fatal errors must supply the callback.

runTask without onProgress drains metadata chunks through the Effect channel (queue allocations and Effect pulls still occur) but does not allocate metadata arrays or fire any callback. collectStream without onProgress performs a data-only drain: no metadata arrays are allocated and no callback is fired, though channel overhead still applies.

License

MIT