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

@vikast908/loaders

v0.2.2

Published

State-aware loading animations built with Web Components, CSS, Canvas 2D, and WebGL.

Readme

@vikast908/loaders

OrbUX loaders for agent and AI interfaces.

This package contains the full loader catalog across CSS, Canvas 2D, and WebGL tiers. Import the package root to register every loader, or import a subpath to register just one.

Install

npm install @vikast908/[email protected] @vikast908/[email protected]

Published on npm as @vikast908/loaders (depends on @vikast908/core). Prefer 0.2.2 or newer. 0.1.0 incorrectly listed @orbux/core@workspace:* and does not install cleanly. In this monorepo after a workspace build, the same imports work via workspace:* linking.

Use

import '@vikast908/loaders/pulse-orb';
import '@vikast908/loaders/pulse-dots';

const orb = document.querySelector('orbux-pulse-orb');
orb.state = 'thinking'; // idle | thinking | streaming | tool-calling | waiting | done | error | cancelled
orb.progress = 0.6;      // optional 0..1 for determinate loaders
orb.pulse();             // optional: call per streamed token to track real throughput

orb.addEventListener('orbux:statechange', (e) => console.log(e.detail.previous, '→', e.detail.state));
@import "@vikast908/loaders/preflight.css";
<!-- show-label renders a visible caption; quiet silences the ARIA live region -->
<orbux-pulse-orb state="streaming" size="140px" show-label label="Generating…"></orbux-pulse-orb>

Every loader reacts to all eight agent states, is themeable through --orbux-* (including --orbux-color-cancelled), and inherits reduced-motion, role="status", debounced screen-reader announcements, and offscreen pause from @vikast908/core. To map an SDK onto the state model, use the @vikast908/core/adapters entry point (Vercel AI SDK, AG-UI, OpenAI streaming).

Subpath exports

Every loader is available as @vikast908/loaders/<id> (for example @vikast908/loaders/ember-flame). The package also exports preflight.css for layout stability before custom elements upgrade.

Standalone HTML

The gallery build writes a self-contained HTML file per loader at apps/site/public/orbux/<id>.html (minified browser bundle inlined). On a detail page: Download HTML saves the file; Copy HTML puts the markup on the clipboard and shows ✓ Copied or Copy failed. You can also open the HTML file in a browser.

Workspace

In this monorepo, after pnpm install and a package build, the same import paths work via workspace:* linking. The package is published from packages/loaders.