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

vite-plugin-instance

v0.1.0

Published

Vite integration for the Instance framework — boot-attribute script injection, .is file compilation through the real Instance Compiler, and the virtual:instance IVC module.

Readme

vite-plugin-instance

Vite integration for the Instance framework.

Instance is a no-build framework — one classic <script> that boots off its own tag attributes. This plugin doesn't change that. It exists for projects already living inside Vite, and does three things:

  1. Injects the Instance script into index.html with your boot attributes (, autoclass, super, …), first in <head>, so the document.currentScript boot contract works exactly like a hand-written tag.
  2. Compiles .is files (the Instance DSL) at dev/build time — through the real Instance Compiler booted headlessly, not a reimplementation — so import './app.is' just works.
  3. Serves virtual:instance — a module retrieving the active Instance via the IVC broker (globalThis[Symbol.for('Instance')]()), so module code never depends on the named global.

Setup

npm i -D vite-plugin-instance
npm i -D jsdom        # only needed if you use .is files

Put your Instance bundle (e.g. Instance-0.87.x.js) in public/.

// vite.config.js
import { defineConfig } from 'vite';
import instance from 'vite-plugin-instance';

export default defineConfig({
  plugins: [
    instance({
      src: '/Instance-0.87.x.js',
      attrs: { '⚡': true, autoclass: 'core, baseline' },
    }),
  ],
});
// any module
import Instance, { ready } from 'virtual:instance';
import './components/hello.is';   // compiled at build time

await ready;
document.body.appendChild(new Hello());

Options

| option | default | meaning | |--------------|--------------------------------|---------| | src | /Instance-0.87.x.js | public path the bundle is served from | | attrs | { autoclass: 'core, baseline' } | boot attributes on the injected tag; true renders a bare attribute | | inject | true | set false if you hand-write the script tag | | compileIs | true | set false to skip .is compilation | | bundlePath | <publicDir> + src | filesystem path to the bundle, for the compiler boot |

Notes

  • The injected tag is a classic script, deliberately — Instance's boot reads document.currentScript attributes, which ES modules don't have. It executes before any module code, so virtual:instance always finds a booted runtime.
  • Compiled .is modules are definition side-effects (classes register against the booted runtime); import them for effect.
  • No build step is required to publish or consume this plugin. It is three files.