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

@rckflr/modelar-live

v0.1.0

Published

Modelar live host: one process = MCP (stdio + HTTP) + studio mirror at http://127.0.0.1:12416 — watch and control an LLM modeling session in real time

Readme

@rckflr/modelar-live

Live host for Modelar — a 3D modeling studio operated by AI agents. One process, three roles:

  1. MCP server — the published modeling tools (create_model, update_model, delete_model, duplicate_model, arrange_models, get_state) run in a QuickJS-WASM sandbox; the skill is fetched from the live origin and SHA-256-verified before every load. The host holds the project state, so tool calls carry no state document.
  2. Studio mirror — every state change is pushed over WebSocket to any open studio tab, so you watch the LLM build in real time in the viewport.
  3. Static server — serves that studio itself at http://127.0.0.1:12416/ (loopback, auto-connects to the mirror).

Use

npx -y @rckflr/modelar-live
# then open http://127.0.0.1:12416/

Wire an MCP client to the same process (shared state, same mirror):

[mcp_servers.modelar-live]
url = "http://127.0.0.1:12416/mcp"
startup_timeout_sec = 30

(Codex also accepts stdio: command = "npx", args = ["-y", "@rckflr/modelar-live"] — that session gets its own host, without a shared mirror.)

Controls (in the studio's Headless live card)

  • Pausar / Reanudar — hold the LLM's next tool call
  • Deshacer última — revert the LLM's last applied tool call
  • Enviar al headless — push the studio's current project into the session

Environment

  • MODELAR_LIVE_PORT (default 12416) — HTTP + WS port
  • MODELAR_ORIGIN (default https://modelar.rckflr.workers.dev) — origin whose llms.txt skill is loaded and whose studio is proxied when no local build exists

Rendering stays in the browser (WebGL): headless builds are real, and the live mirror is where you see them.