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

@omnidraw/function-runtime

v0.6.0

Published

Portable direct function execution and resource-call contracts for Omnidraw.

Readme

OmniDraw

Run your real apps in an infinite drawing canvas. Generate apps with ai. Reuses your llm subscriptions.

The project is organized as a monorepo and follows a Functional Core / Imperative Shell architecture.

Quick Start

OmniDraw is currently run from source. Install Bun 1.3.14, then run:

git clone https://github.com/omnidraw/omnidraw.git
cd omnidraw
bun install
bun run dev

Open the frontend URL printed by the development runner (by default http://127.0.0.1:3002).

For a production-style local run, build the workspace and start the single Bun server:

bun run server:prod

This builds the frontend and serves its static SPA assets, API, WebSocket, and file routes together at http://localhost:7496.

You can edit the canvas from the UI, or from the CLI. Agents can use the same canvas CLI surface for scripted canvas changes.

Useful CLI commands during local development:

bun run apps/cli/src/main.ts --version
bun run apps/cli/src/main.ts --help
bun run apps/cli/src/main.ts canvas --help

Database

  • Omnidraw keeps one home at ~/.omnidraw; its primary Turso database is ~/.omnidraw/main.db.
  • In dev mode it the databas is in /.omnidraw/main.db local to the current folder.
  • --data-dir <path> selects another home and takes precedence over OMNIDRAW_HOME.

Debugging the live app

The canvas runtime includes a built-in debug logger that can be enabled per plugin or per service from the browser devtools console.

Debug keys use this format:

omnidraw:debug:<plugin|service>:<name>

Levels:

  • 0, false, off, or empty = disabled
  • 1 = important lifecycle logs
  • 2 = more detailed state/layout logs
  • 3 = very noisy per-frame/per-event logs

Examples:

// hosted component plugin logs
localStorage.setItem("omnidraw:debug:plugin:hosted-component", "3")

// camera service logs
localStorage.setItem("omnidraw:debug:service:camera", "1")

Then reload the page and inspect the browser console.

To turn a target back off:

localStorage.setItem("omnidraw:debug:plugin:hosted-component", "0")

Current log output includes prefixes like:

[omnidraw][plugin:hosted-component][L2] ...

This is especially useful for debugging live layout, overlay, hydration, transform, and mount issues inside the running app.

For implementation conventions and deeper subsystem docs, read:

License

MIT. See LICENSE.