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

panelty

v0.1.4

Published

A tab + panel workspace for Svelte: split, drag, tear off, and hand every gesture to a host you own.

Readme

panelty

A tab + panel workspace for Svelte 5.

Split a panel, drag one onto another's edge, tear one off onto the tab bar, drag the seam between two. What panelty does not do is decide what any of that MEANS: it holds no tree and writes nothing. It draws the arrangement you hand it, recognises the gesture over it, and raises the gesture at a host you implement — so persistence, concurrency, undo and what a tab is called are yours.

<script lang="ts">
	import { Tabs, Panels, workspace, memoryHost, registerPanel } from 'panelty';
	import 'panelty/tokens.css';

	registerPanel({ id: 'notes', title: 'Notes', component: Notes });
	workspace().configureHost(memoryHost({ defaultPanelType: 'notes' }));
</script>

<Tabs />
<Panels />

The three shapes

<Tabs> alone is a tab strip. <Panels> alone is a splittable panel tree. <Panels> inside <Tabs> is a workspace — and only there do the cross-boundary drags exist, because the drag bus one publishes is what the other looks for. There is no enableTabDragging flag: a gesture that spans two components you did not compose is not disabled, it is unexpressible.

The host

Two contracts, each naming only what its own component can trigger. TabHost is panel-free by construction; PanelHost is tab-free. Every method answers whether the write LANDED — a refusal is ordinary (closing a tab's last panel, a peer having taken what the gesture names) and the panel system uses the answer to decide where to put the focus, never to retry.

memoryHost() is one that keeps the tree in memory and hands it straight back. It is the whole of the contract implemented over a plain tree — useful on its own, and the thing that proves the port is complete.

The panels

Yours. registerPanel({ id, title, icon, component }) takes any component honouring PanelProps; nothing in here knows what one draws. A panel gets its id, its persisted state bag, and a setState that routes back through your host.

Styling

Every rule reads var(--panelty-x, var(--panelty-x-default)). Import tokens.css for the look it ships with, then set --panelty-* to wear your own — on :root, on a subtree, or on one instance. See src/lib/ui/tokens.css: it is the contract, and it documents itself.

Icons work the same way: the chrome vendors the ten glyphs it draws, and registerIcons(table) hands over yours for the panel types and menu rows you name.

MIT.