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

@clipkit/editor

v1.1.0

Published

The Clipkit editor — one configurable, registry-driven editor over the Source schema. BASIC and ADVANCED ship as configurations of the same component tree (<Editor configuration={…}>), powered by @clipkit/editor-core.

Downloads

176

Readme

@clipkit/editor

One configurable React editor over the Source schema, spanning BASIC to ADVANCED modes.

npm install @clipkit/editor

The ClipKit editor is a single component tree—two modes (BASIC and ADVANCED) are just different configurations of the same <Editor>. The editor renders a four-panel layout (assets/layers on the left, canvas center, inspector right, timeline bottom) and is powered by @clipkit/editor-core. Storage is an injected AssetStore port, so you wire your own backend (or use the included in-memory and IndexedDB options). It requires React 19 and a stylesheet import.

Usage

import { Editor, BASIC_CONFIGURATION } from '@clipkit/editor';
import '@clipkit/editor/styles.css';

export function MyEditor({ source }) {
  return (
    <Editor
      initialSource={source}
      configuration={BASIC_CONFIGURATION}
      onSourceChange={(updated) => console.log(updated)}
    />
  );
}

API

Components

  • Editor — Main editor component. Takes initialSource (required), configuration, assetStore, onSourceChange, onRender, and render/theme props.
  • ExportDialog — Modal for export format/resolution/quality selection. Consumer calls onConfirm with the user's choice; the editor has no knowledge of how to render it.

Configurations

  • BASIC_CONFIGURATION, ADVANCED_CONFIGURATION — Pre-built editor layouts controlling visible panels (assets, layers, timeline).

Hooks

  • useEditor() — Returns actions (play, seek, undo, select, etc.) and current playback state.
  • useEditorStore() — Direct access to the editor's Zustand store.

Storage

  • createLocalAssetStore() — IndexedDB-backed media bin (persists in browser, no backend).
  • createMemoryAssetStore() — In-memory media bin (loses assets on reload).

Other

  • EDITOR_COMMANDS — Keyboard command registry (play/pause, undo/redo, frame stepping).
  • Section, FieldRow — UI components for building custom inspector panels.

License

Apache-2.0 · part of ClipKit · source