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

mpa-vite-plugin

v1.0.0

Published

A Vite plugin for multi-page static sites.

Readme

mpa-vite-plugin

A Vite plugin for multi-page static sites.

Vite's built-in MPA support has two problems:

  • Dev server doesn't route /settings to src/pages/settings/index.html
  • Build output paths ignore your entry keys and use the full source path instead

This plugin fixes both.

Website

emperor-of-mars.github.io/mpa-vite-plugin

Install

npm install mpa-vite-plugin

Local development install

If you're installing from a local path:

npm install file:/absolute/path/to/mpa-vite-plugin

Setup

Create your pages:

src/
└── pages/
    ├── index/
    │   ├── index.html
    │   └── index.ts
    └── settings/
        ├── index.html
        └── index.ts

Add the plugin to your vite.config.ts:

import { defineConfig } from 'vite'
import multivite from 'mpa-vite-plugin'

export default defineConfig({
  plugins: [multivite()]
})

Dev

vite --configLoader runner

you cann add this to your package.json

"scripts": {
  "dev": "vite --configLoader runner"
}

Visit http://localhost:5173/ and http://localhost:5173/settings.

Build

vite build

Output:

dist/
├── index.html
├── settings.html
└── assets/

Options

multivite({ pagesDir: 'src/pages' }) // default

How it works

Three Vite plugin hooks:

  • config — discovers pages and injects them as Rollup entry points
  • configureServer — rewrites URLs in dev so /settings serves the right HTML file
  • generateBundle — remaps output paths from the deep source structure to a clean flat layout

package.json requirements

Your plugin's package.json must have the correct name, main, and types fields:

{
  "name": "mpa-vite-plugin",
  "type": "module",
  "main": "./dist/index.js",
  "types": "./dist/index.d.ts"
}

Building

After cloning, compile before use:

npm install
npm run build

This compiles src/index.ts to dist/. The dist/ folder is not committed to the repo.