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

@place-ts/devtools

v0.1.1

Published

In-app developer tools — a dev-only island that observes the reactive graph, islands, routing, and load performance. NOT a platform system; a curated dev package.

Readme

@place-ts/devtools

See the running app from inside it — the reactive graph, the islands, the route, the JS weight.

A dev-only island. The package exports the devtools view; the island() call has to live in a file under your own project tree (the island bundler requires it). Wrap it in a one-line island file:

// src/islands/devtools.tsx
import { island } from '@place-ts/component'
import { devtoolsView } from '@place-ts/devtools'

export default island(import.meta.url, devtoolsView)

islandsDir discovery picks that file up automatically. Then render it once in your root layout:

import Devtools from './islands/devtools.tsx'

// …in the layout view, near the end of <body>:
<Devtools client="idle" />

A floating launcher appears in the corner; click it for the panel.

| Panel | Shows | |---|---| | Graph | Every state / derived / watch node — value, status, dependency edges. Live, via @place-ts/reactivity's inspectGraph(). | | Islands | Every island on the page — load strategy, hydration state. | | Routes | The active route — path, params, query. | | Console | Captured console output — errors, warnings, info, log — plus uncaught errors and unhandled rejections. | | Perf | Page load timing + the JavaScript the page shipped. |

The devtool runs as a place island — it dogfoods the framework. It ships its own self-contained stylesheet (CSP-safe, adopted via a constructable CSSStyleSheet) and never touches your app's theme or layout.

See docs/00-charter.md for scope + non-goals.