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

@roomy-ai/apps

v0.2.6

Published

Roomy-shipped built-in apps. Synced to ~/Roomy/.apps/ on server start and mounted into every sandbox at /opt/roomy-apps/.

Readme

@roomy-ai/apps

Roomy-shipped built-in apps. Each *.app/ directory in this package is a complete Roomy app — the same structure that roomy-agent app create produces in a workspace — pre-built so dist/ is shipped alongside source.

On server start, runtime.writeBuiltinApps(home) copies every <name>.app/ here into ~/Roomy/.apps/<name>.app/ (overwriting), then the sandbox mount plan binds ~/Roomy/.apps/ read-only at /opt/roomy-apps/. Agents attach built-in fragments via the regular roomy-agent chat attach-artifact command using paths under /opt/roomy-apps/.

Adding a built-in app

The intended workflow is to build the app via Roomy itself (dogfood), then promote the workspace output into this package:

  1. Open a Roomy chat in any workspace.
  2. Ask Roomy to build the app (e.g. chat-forms.app with a yes_no fragment).
  3. Iterate until the workspace app is correct.
  4. Copy <workspace>/.chats/<chatId>/artifacts/<name>.app/ into packages/apps/<name>.app/.
  5. Commit. The next server start syncs it into ~/Roomy/.apps/.

Constraint

All built-in apps must use @roomy-ai/ui for every UI primitive — no raw HTML elements where a UI component exists, no second component library. If a primitive is missing, add it to @roomy-ai/ui first.