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

@karaoke-cms/contracts

v0.18.1

Published

Shared type contracts for karaoke-cms — interfaces for modules, themes, and configuration

Readme

@karaoke-cms/contracts

Shared type contracts for karaoke-cms. Every interface that crosses a package boundary — modules, themes, configuration, menus, CSS contracts — is declared here. All other karaoke-cms packages import from this package rather than from each other.

Installation

npm install @karaoke-cms/contracts

Module and theme authors use this package as a peer dependency. End users typically don't install it directly — it is a dependency of @karaoke-cms/astro.

Usage

import { defineModule, defineTheme } from '@karaoke-cms/contracts';
import type { ModuleInstance, ThemeInstance, KaraokeConfig } from '@karaoke-cms/contracts';

Configuration

defineModule(def)

Define a karaoke-cms module. Returns a factory function — call the factory with { mount } to get a ModuleInstance.

import { defineModule } from '@karaoke-cms/contracts';

export const myModule = defineModule({
  id: 'my-module',
  cssContract: {
    'my-card': { description: 'Module card wrapper', required: true },
  },
  routes: (mount) => [
    { pattern: mount, entrypoint: '@my-org/my-module/pages/index' },
  ],
  menuEntries: (mount, id) => [
    { id, name: 'My Module', path: mount, section: 'main', weight: 50 },
  ],
});

// In karaoke.config.ts:
// modules: [myModule({ mount: '/my-module' })]

defineTheme(def)

Define a karaoke-cms theme. Returns a factory function — call the factory to get a ThemeInstance.

import { defineTheme } from '@karaoke-cms/contracts';

export const myTheme = defineTheme({
  id: 'my-theme',
  toAstroIntegration: (config, modules) => ({
    name: 'my-theme',
    hooks: {
      'astro:config:setup': ({ injectRoute }) => {
        injectRoute({ pattern: '/', entrypoint: '...' });
      },
    },
  }),
});

// In karaoke.config.ts:
// theme: myTheme()

Key exported types

| Export | Description | |--------|-------------| | KaraokeConfig | Full config shape for defineConfig() in karaoke.config.ts | | ModuleInstance | Resolved module — returned by any module factory call | | ThemeInstance | Resolved theme — returned by any theme factory call | | CssContract | Record mapping CSS class names to { description, required } | | DocsSection | One entry in the docs([...]) array-form call | | ModuleMenuEntry | Menu entry registered by a module instance | | CommentsConfig | Giscus comments configuration shape | | ResolvedMenus | Resolved menu structure available at build time | | RouteDefinition | { pattern, entrypoint } pair passed to injectRoute |

What's new in 0.18.0

  • ModuleInstance.modes — added modes?: ('dev' | 'prod')[] to ModuleInstance. Modules can now declare which build modes they participate in directly, replacing external collections.yaml overrides for dev/prod control.

What's new in 0.17.0

  • DocsSection.comments — added comments?: boolean to DocsSection so the array-form docs([...]) can set per-section comment defaults.
  • DocsSection.parent — added parent?: string to DocsSection for nesting docs sections as submenus in the main nav.
  • DocsSection.weight — added weight?: number for explicit menu ordering. Reserved weights: Blog = 10, Tags = 30.
  • MenuEntryConfig.static — added static?: string for non-interactive text labels in menus.yaml.
  • MenuEntryConfig.parent — added parent?: string for submenu nesting in menus.yaml.
  • ModuleInstance.meta — added meta?: Record<string, unknown> for modules to pass config through the core without modifying KaraokeConfig.
  • KaraokeConfig.modules accepts (ModuleInstance | ModuleInstance[])[] — array-returning factories (e.g. docs([...])) can be passed directly; karaoke() flattens them automatically.