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

@nvoi/console

v1.0.4

Published

Embedded AI console widget for nvoi sandboxes. Injects into arbitrary host apps via CF Worker — CSS fully isolated from the host.

Downloads

405

Readme

@nvoi/console

Embedded AI console widget for nvoi sandboxes. Injects into arbitrary host apps via CF Worker — CSS fully isolated from the host.

Install

npm install @nvoi/console

Usage (esm.sh — production)

<script type="module">
  import "https://esm.sh/@nvoi/console/browser";

  window.NVOI_CONSOLE_CONFIG = {
    sandboxId: "123",
    apiUrl: "https://example.com/api",
    transport: {
      type: "phoenix",
      url: "wss://example.com/socket",
      token: "JWT_TOKEN"
    }
  };
</script>

Usage (script tag drop-in)

<script>
  window.NVOI_CONSOLE_CONFIG = {
    sandboxId: "123",
    apiUrl: "https://example.com/api",
    transport: {
      type: "phoenix",
      url: "wss://example.com/socket",
      token: "JWT_TOKEN"
    }
  };
</script>
<script src="https://esm.sh/@nvoi/console/browser"></script>

CSS Isolation

The console injects into host apps that have their own CSS (including Tailwind). Three-layer isolation prevents bleed in either direction:

Layer 1 — Cascade reset (@layer nvoi-isolation) Declared as the lowest-priority cascade layer. all: revert-layer on #nvoi-console-root * wipes any host styles that would bleed in via element/universal selectors.

Layer 2 — Prefixed utilities (nc: prefix) All console component classes use Tailwind with prefix(nc). The host's unprefixed .flex and our nc:flex never collide.

Layer 3 — Streamdown scoped rules (unlayered + !important) Streamdown (markdown renderer) uses hardcoded Tailwind classes internally. We provide matching CSS rules scoped to #nvoi-console-root .{class} { ... !important } — they only match inside our root and can't leak out. CSS variables (--color-background, --color-border, etc.) map Streamdown's theme tokens to our dark palette.

Cascade priority (high → low)

!important unlayered     → Streamdown scoped rules
@layer utilities         → nc: prefixed Tailwind (our components)
@layer base              → Tailwind normalize
@layer nvoi-isolation    → all: revert-layer (wipes host bleed)

Build

npm run build:pkg    # ESM + CJS + browser IIFE
npm run build:types  # TypeScript declarations
npm run release      # lint + test + typecheck + build:pkg + build:types

Publish

npm run release
npm publish --access public