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

@overkube/web

v0.1.6

Published

overkube's page: the registry of the dashboard's kinds, the addons run in it (their lifecycle), the cluster they are given, and the frame that draws what they define — for a host to boot into a page of its own

Readme

@overkube/web

overkube's page: what the browser runs. Started in order (src/boot.ts): signed in as its server says one signs in here (GET /auth; src/session.tsx: not signed in, the sign-in screen alone); the connector to the gateway at /kube (@overkube/connector) and the source answering queries over it (@overkube/source); overweave's registry of the dashboard's kinds (@overkube/sdk); the user's changes read back (@overkube/shell's UserService, in localStorage); the addons run in it (src/host: their lifecycle — requirements, retries, ?safe runs the core alone); the shell drawn into #app (?debug: the slots over it). The addons in its bundle: src/addons.ts — the core, metrics, cert-manager, trivy, helm, flux.

npm run dev -w @overkube/web      # Vite, with /kube and /auth passed to OVERKUBE_SERVER (http://127.0.0.1:8080)
npm run build -w @overkube/web    # dist/: what the server serves as OVERKUBE_UI

The dev stand (make dev) runs the first at http://localhost:5173; the image copies the second to /app/ui. vite.config.ts reads the workspace's packages and overweave from their sources (the overkube-source and overweave-source conditions), one Preact.

For a host that draws the page into a page of its own (a platform's plugin), it is published as a library, @overkube/web (src/index.ts): boot({ element, asked, gateway, headers, signIn: false, addons }) — its gateway where the host serves it, the host's headers on every request (a CSRF token), no /auth asked (the host has signed the user in), the host's own addons beside the page's; it answers the registry and close(). Its own packages (the addons, the shell, the runtime, the source, the connector) are bundled in; those a host's addons are written with — @overkube/sdk, @overkube/uikit, @overkube/kube-types, @overkube/query, @overkube/gateway, overweave, Preact — are dependencies, one of each in the host's bundle. @overkube/web/styles is the page around it (the fonts, src/page.css), for the host's bundler.

import { boot } from '@overkube/web';
import '@overkube/web/styles';

const page = await boot({ element, asked: new URLSearchParams(location.search), gateway: '/plugins/overkube/kube', signIn: false });
npm run build:lib -w @overkube/web   # lib/: the library (vite.lib.config.ts), its types