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-rebundle

v2.0.7

Published

Vite plugin that forces single-file output per entry. Ensures each entry point is bundled into a standalone file without code-splitting.

Readme

vite-plugin-rebundle

A Vite plugin that guarantees one standalone file per entry point. It rebundles each entry into a single file with no shared chunks or dynamic imports. Requires Vite 8+.

Why?

Vite does not provide single-file output for multi-entry builds. When code splitting is needed, each entry can produce extra chunks and dynamic imports.

vite-plugin-rebundle solves that by taking Vite's build output and rebundling each entry with rolldown. It runs only during vite build and does not affect the dev server.

Installation

npm install -D vite-plugin-rebundle

Usage

Add the plugin to your Vite config:

import { defineConfig } from 'vite'
import { rebundle } from 'vite-plugin-rebundle'

export default defineConfig({
  plugins: [rebundle()],
  build: {
    rolldownOptions: {
      input: {
        bundle1: 'src/bundle1.js',
        bundle2: 'src/bundle2.js',
      },
      output: {
        entryFileNames: '[name].js',
      },
    },
  },
})

Configuration

rebundle() accepts up to two arguments:

  • The first argument contains global rolldown input and output options applied to every entry.
  • The second argument contains per-entry options that are deep-merged with the global ones.
export default defineConfig({
  plugins: [
    rebundle(
      // Global options applied to all bundles
      {
        input: {...},
        output: {...},
      },
      // Per-entry options, will be deep-merged with global options
      {
        bundle1: {
          input: {...},
          output: {...},
        },
        bundle2: {
          input: {...},
          output: {...},
        },
      },
    ),
  ],
  build: {
    rolldownOptions: {
      input: {
        bundle1: 'src/bundle1.js',
        bundle2: 'src/bundle2.js',
      },
      output: {
        entryFileNames: '[name].js',
      },
    },
  },
})

How it works

When you run vite build, vite-plugin-rebundle:

  1. Lets Vite perform the normal build.
  2. Rebundles each entry with rolldown.
  3. Writes back a single self-contained JavaScript file per entry.

Watch Mode

When running in build watch mode, the plugin exposes import.meta.env.REBUNDLE_PORT. You can use it to listen for rebundle events over WebSocket:

const ws = new WebSocket(`ws://localhost:${import.meta.env.REBUNDLE_PORT}`)
ws.addEventListener('message', e => console.log('Rebundle event:', e.data))

Notes

Source maps are not currently supported. If you pass sourcemap option, it will be ignored.