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

@cimi-cms/cli

v0.1.0-beta.0

Published

CIMI command-line tools: schema pull/diff/push and TypeScript type generation.

Readme

@cimi-cms/cli

Command-line tools for CIMI: schema pull/diff/push and TypeScript type generation. Pairs with @cimi-cms/schema (definitions + inference) and @cimi-cms/sdk (typed content client).

npm i -D @cimi-cms/cli

Setup

// cimi.config.ts — the token is NEVER stored here
import { defineConfig } from '@cimi-cms/cli';

export default defineConfig({
  appId: process.env.CIMI_APP_ID!,
  apiUrl: 'https://cimi.co.nl/api/v1',
  schema: './cimi/schema/index.ts', // presence ⇒ managed mode; omit for typegen-only
  output: './src/cimi/cimi.generated.ts',
});
export CIMI_API_TOKEN=cimi_…   # scope `read` for types/pull, `read`+`manage` for push

Commands

| Command | What it does | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | cimi init [--force] | Bootstrap defineBlock/defineSection/defineContentType modules from the live app into cimi/schema/ | | cimi pull | Write the live schema to cimi.schema.json (PR-diffable snapshot) | | cimi diff | Local definitions vs the live app | | cimi push [--dry-run] [--prune] [--yes] | Apply local definitions; deletes only with --prune; the server recomputes the diff and refuses stale pushes (409) | | cimi types [--check] [--watch] | Generate cimi.generated.ts — from local definitions when managed, from the live schema otherwise | | cimi check | types --check — the CI entry, exit 1 on drift |

Managed mode in one minute

npx cimi init      # pull the current model into code
npx cimi diff      # should print "No changes"
npx cimi push      # the app is now managed: the admin block builder turns read-only

Renames are explicit: add renamedFrom: 'old-key' to the renamed definition and push — stored content migrates with the key. Never guessed from similarity.

Full model: docs/SCHEMA_AS_CODE.md in the CIMI repository.

MIT © Wouters Media