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

@mr_hugo/vite-plugin-boredom

v0.1.0

Published

Vite plugin for multi-file boreDOM development with single-file deployment

Downloads

49

Readme

@mr_hugo/vite-plugin-boredom

Experimental Vite plugin for multi-file boreDOM authoring with single-file deployment output.

Use this plugin only when you intentionally opt into boreDOM's experimental multi-file workflow. The default boreDOM path is still single-file, zero-build development.

Installation

npm install -D @mr_hugo/vite-plugin-boredom@next

Usage

Vite Configuration

// vite.config.js
import { defineConfig } from 'vite';
import { boredomPlugin } from '@mr_hugo/vite-plugin-boredom';

export default defineConfig({
  plugins: [
    boredomPlugin({
      inlineRuntime: true,
      validateComponents: true,
      optimizeStyles: true,
      // Optional: override which files are scanned for components
      componentInclude: [/\.component\.js$/],
      componentExclude: ['/legacy/']
    })
  ],
  
  build: {
    rollupOptions: {
      input: {
        main: 'index.html',
        dashboard: 'pages/dashboard.html'
      },
      output: {
        manualChunks: undefined,
        inlineDynamicImports: true
      }
    },
    cssCodeSplit: false
  }
});

Component Structure

Create components as ES modules:

// components/ui/Button.js
export const metadata = {
  name: 'ui-button',
  version: '1.0.0',
  dependencies: [],
  props: ['variant', 'size', 'disabled'],
  events: ['click']
};

export const style = `
  @layer components.ui-button {
    ui-button button {
      padding: 8px 16px;
      border: none;
      border-radius: 4px;
      cursor: pointer;
    }
    ui-button[variant="primary"] button {
      background: #007bff;
      color: white;
    }
  }
`;

export const template = `
  <button 
    data-dispatch="click"
    data-class="disabled:local.disabled"
    data-text="local.label || 'Button'"
  ></button>
`;

export const logic = ({ on, local }) => {
  local.variant = local.variant || 'default';
  local.disabled = local.disabled || false;
  local.label = local.label || 'Button';

  on('click', ({ e, local }) => {
    if (local.disabled) return;
    e.dispatcher.dispatchEvent(new CustomEvent('ui-button:click', {
      bubbles: true,
      detail: { variant: local.variant }
    }));
  });
};

Development Setup

// main.js
import { loadComponent, registerComponentPath } from '@mr_hugo/vite-plugin-boredom/component-loader';
import * as Button from './components/ui/Button.js';

async function initApp() {
  registerComponentPath('ui-button', Promise.resolve(Button));
  await loadComponent(Button);
}

initApp();

HTML Template

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <title>My App</title>
</head>
<body>
  <script id="initial-state" type="application/json">
    { "user": { "name": "John" } }
  </script>

  <ui-button></ui-button>

  <script type="module" src="./main.js"></script>
  <script src="./boreDOM.js" data-state="#initial-state"></script>
</body>
</html>

Plugin Options

  • inlineRuntime (boolean, default: true) - Inline boreDOM runtime into HTML
  • validateComponents (boolean, default: true) - Validate component exports and metadata (emits Vite warnings)
  • optimizeStyles (boolean, default: true) - Optimize CSS output
  • componentInclude (string | RegExp | (id) => boolean or array, default: all .js/.mjs/.cjs) - Select files the plugin should inspect for components
  • componentExclude (string | RegExp | (id) => boolean or array, default: node_modules) - Exclude files from component inspection

Build Output

The plugin transforms your multi-file development setup into a single HTML file:

<!DOCTYPE html>
<html>
<body>
  <ui-button></ui-button>
  
  <!-- Auto-generated component triplets -->
  <style data-component="ui-button">...</style>
  <template data-component="ui-button">...</template>
  <script type="text/boredom" data-component="ui-button">...</script>
  
  <script data-state="#initial-state">
    /* inlined boreDOM runtime */
  </script>
</body>
</html>

Development vs Production

  • Development: Multi-file with HMR, component reloading
  • Production: Single HTML file, fully self-contained
  • Deployment: Zero dependencies, works anywhere

Experimental Status

The plugin and dev-time loader are evolving. Validate generated output (npx @mr_hugo/boredom validate) and pin versions if you need repeatable CI behavior.

Component Dependencies

Components can depend on other components:

export const metadata = {
  name: 'ui-modal',
  dependencies: ['ui-button', 'ui-overlay']
};

Dependencies are automatically loaded in the correct order.

License

ISC