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

@ebay/muse-vanilla-vite-plugin

v2.0.0

Published

Vite plugin for MUSE vanilla (init/boot) plugins with IIFE build output

Readme

@ebay/muse-vanilla-vite-plugin

Vite plugin for MUSE vanilla (init and boot) plugins. Encapsulates the standard Vite configuration so projects don't need to repeat it — just add the plugin to vite.config.js.

Usage

// vite.config.js
import { defineConfig } from 'vite';
import museVanillaVitePlugin from '@ebay/muse-vanilla-vite-plugin';

export default defineConfig({
  plugins: [museVanillaVitePlugin()],
});

What it configures

Build

  • Entry: src/main.js
  • Output: build/dist/main.js (or build/dist/boot.js for boot plugins)
  • Format: iife
  • Source maps enabled

The output filename is determined automatically from muse.type in the project's package.json:

| muse.type | Output file | |-------------|-------------| | boot | boot.js | | anything else | main.js |

Dev server

Configured via environment variables:

| Variable | Description | |---|---| | PORT | Dev server port; also sets strictPort: true | | MUSE_LOCAL_HOST_NAME | Dev server hostname (default: localhost) | | HTTPS | Set to true to enable HTTPS | | SSL_CRT_FILE | Path to SSL certificate (default: node_modules/.muse/certs/muse-dev-cert.crt) | | SSL_KEY_FILE | Path to SSL key (default: node_modules/.muse/certs/muse-dev-cert.key) |

Overriding defaults

Any config keys set directly in vite.config.js take precedence over the plugin's defaults:

export default defineConfig({
  plugins: [museVanillaVitePlugin()],
  build: {
    // override: disable source maps
    sourcemap: false,
  },
});

Dev Guide

  1. Link the package globally from this directory:
pnpm link -g
  1. Go to a plugin project root and link it:
pnpm link @ebay/muse-vanilla-vite-plugin
  1. Start the dev server:
pnpm start