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

anywidget-bundle

v0.1.1

Published

Build manifest-backed anywidget module graphs with Vite.

Readme

anywidget-bundle

The Vite plugin builds a bundle app into a lean anywidget entry and JavaScript chunks that can be served from a Python wheel.

pnpm add -D anywidget-bundle vite
import anywidgetBundle from "anywidget-bundle";

anywidgetBundle({ app: "./src/widget.ts", outDir: "./src/my_widget/static" });

Run pnpm exec vite build before building the consumer wheel.

Type the app against the bundle lifecycle contract:

import type { AnyWidgetBundleApp } from "anywidget-bundle";

export default {
  render({ el }) {
    el.textContent = "ready";
  },
} satisfies AnyWidgetBundleApp<{}>;

Each build writes:

  • anywidget.json, which identifies the entry, app, stylesheet, and JavaScript module allowlist
  • index.js, the self-contained anywidget bootstrap
  • chunks/app.js and opaque chunks/chunk-[hash].js files imported by the app
  • widget.css when the app imports CSS

Set output.entry, output.app, or output.style to change these artifact paths. Configured artifact paths use portable ASCII names and cannot collide. The Vite API defines the full path contract.

The Python Bundle reads anywidget.json, gives index.js to anywidget, and serves manifest-listed modules to the bootstrap through the widget model. Static modules load during model initialization. Literal relative dynamic imports load when executed. A bundle app initialize hook may return a cleanup function or undefined.

Read the documentation.