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

@lynx-js/vanilla-rsbuild-plugin-canary

v0.1.0-canary-20260829-0a524389

Published

An Rsbuild plugin for building Vanilla Lynx applications with Element PAPI.

Readme

@lynx-js/vanilla-rsbuild-plugin

An Rsbuild plugin for building Vanilla Lynx applications directly with Element PAPI.

Usage with Rspeedy

import { defineConfig } from '@lynx-js/rspeedy'
import { pluginVanillaLynx } from '@lynx-js/vanilla-rsbuild-plugin'

export default defineConfig({
  plugins: [
    pluginVanillaLynx({
      entries: {
        card: {
          mainThread: './src/card/main-thread.ts',
          background: './src/card/background.ts',
          css: './src/card/style.css',
        },
      },
    }),
  ],
})

For a convention-based entry, source.entry points to the main-thread source:

export default defineConfig({
  source: {
    entry: {
      card: './src/card/main-thread.ts',
    },
  },
  plugins: [pluginVanillaLynx()],
})

The plugin discovers these optional sibling files:

src/card/
  main-thread.ts
  background.ts
  style.css

background.ts runs in the background JavaScript thread. Element PAPI tree creation and mutation must stay in main-thread.ts.

Use an explicit entries item when the two thread sources are in different directories. Set background: false for a main-thread-only card. Explicit entries take precedence over source.entry.

Entry sources are module requests and use Rspeedy or Rsbuild resolution, including aliases and configured extensions. Automatic sibling discovery is a filesystem convention: it runs only when mainThread names an existing local file. When mainThread is an alias or package request, configure background and css explicitly when they are needed.

The plugin emits one .bundle per logical entry, marks the main-thread asset for Lepus encoding, wraps only the native background asset, and enables the event-handler config required by Element PAPI listeners. HMR and live reload are disabled because Vanilla Lynx does not currently install a compatible hot-update runtime.

When Rspeedy configures both web and lynx environments, the plugin emits a web-encoded [name].web.bundle and a native [name].lynx.bundle. Background JavaScript is runtime-wrapped only for native Lynx; the web encoder embeds the unwrapped background chunk for the web runtime.

Options

pluginVanillaLynx({
  entries: {
    card: {
      mainThread: './src/card/main-thread.ts',
      background: './src/card/background.ts',
    },
  },
  engineVersion: '3.5',
  bundleFilename: '[name].bundle',
})

When bundleFilename is omitted, the plugin uses Rspeedy's output.filename.bundle. Outside Rspeedy it defaults to [name].[platform].bundle.