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

@nbt-dev/devtools

v0.1.1

Published

Drop-in React devtools panel (console logs, live data browser, entity graph, source editor) for apps backed by an NBT console.

Downloads

1,532

Readme

@nbt-dev/devtools

A drop-in React devtools panel for any frontend backed by an NBT console. It gives you, against the live daemon:

  • Console — streaming server logs (/_console/logs/ws)
  • Data — a live, virtualized browser over every installed cartridge's entities, streamed off the bulk WebSocket (/_ws/bulk) with search + row detail
  • Diagram — an entity-relationship graph with live row counts
  • Sources — a dev-mode NBT source editor with diagnostics and apply support
  • Settings — General (devtools panel font), Editor (theme, font size, line wrapping, tab size) and Integrations (mirror a cartridge into a Google Sheet). Preferences persist per operator on the console (server-side), with a localStorage fallback for unauthenticated/dev use.

It assumes your app uses NBT auth: the data socket reads the current session bearer from POST /api/auth/session/current (sent with credentials: "include"), same as the console inspector.

Install

npm install @nbt-dev/devtools

react and react-dom (>=18) are peer dependencies.

Usage

Mount the panel once near your app root — that's it, no stylesheet import:

import { NimbitDevTools } from "@nbt-dev/devtools";

export default function App() {
  return (
    <>
      <YourApp />
      {/* Empty string => same-origin. Point at the console otherwise. */}
      <NimbitDevTools apiBaseUrl="https://console.example.com" />
    </>
  );
}

The panel renders nothing until toggled. It owns the built-in shortcuts Ctrl+F12 and Ctrl/Cmd+Shift+D. You can also toggle it from anywhere:

import { toggleDevTools } from "@nbt-dev/devtools";

toggleDevTools();
// or, with no import: window.dispatchEvent(new CustomEvent("devtools-toggle"))

Next.js

NimbitDevTools is a client component (the bundle carries a "use client" banner). Render it inside a client boundary / your root layout's client tree.

Styling

The panel mounts inside its own shadow root attached to <body>, with its stylesheet injected into that shadow root. Nothing leaks in or out: the host app's CSS (and theme/<html> font-size) can't reach the panel, and the panel's styles can't touch the host. Sizing is pinned to absolute pixels, so the panel renders identically no matter how the host themes its document.

The standalone @nbt-dev/devtools/styles.css export is still published for advanced/manual mounting, but is not needed for normal usage.

API

| Export | Description | | --- | --- | | NimbitDevTools | The panel. Props: apiBaseUrl?, defaultActiveTab?. | | toggleDevTools() | Dispatches the devtools-toggle window event. | | useDevToolsOpen() | Reactive open/closed state for your own toolbar button — works outside the panel, no provider needed. | | DevToolsProvider, useDevTools | Lower-level state if you compose DevTools yourself. | | DevToolsConfigProvider, useDevToolsConfig | The apiBaseUrl config context. | | DevTools | The bare panel (expects the providers above). |