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

@manicjs/bundler

v0.0.3

Published

Readme

@manicjs/bundler

Standalone Bun + OXC build spine extracted from Manic.

Use this package if you want to build your own framework/runtime while reusing the Manic build pipeline primitives.

What it provides

  • buildApplication() pipeline orchestration
  • bundler utilities: resolver, countRoutes, getDirSize, minifyDir, formatSize, formatTime
  • plugin/provider hook contracts
  • CLI entrypoint: manic-bundler build

Installation

bun add @manicjs/bundler

Quick start

import { buildApplication, type PageRoute } from '@manicjs/bundler';

const config = {
  mode: 'fullstack',
  app: { name: 'My Framework App' },
};

await buildApplication({
  config,
  dist: '.dist',
  runLint: true,
  writeRoutesManifest: async () => {
    // your manifest writer
  },
  discoverPageRoutes: async (): Promise<PageRoute[]> => {
    // your route discovery
    return [];
  },
  clientPlugins: [],
  serverPlugins: [],
  plugins: [],
  providers: [],
  onPending: msg => console.log(`[bundler] ${msg}`),
  onSuccess: msg => console.log(`[bundler] ${msg}`),
  onError: msg => console.error(`[bundler] ${msg}`),
});

CLI usage

manic-bundler build bundler.config.ts

Example bundler.config.ts:

export default {
  config: {
    mode: 'fullstack',
    app: { name: 'Standalone App' },
  },
  dist: '.dist',
  clientPlugins: [],
  serverPlugins: [],
};

Build contract assumptions

By default, the pipeline expects:

  • app entry resolved from ./app/main
  • server entry at ./~manic
  • API entries at app/api/**/index.ts (when mode is not frontend)

If your framework layout differs, wrap/adapt route discovery and entry generation around buildApplication().

Plugin/provider hooks

BundlerPlugin

  • name: string
  • preload?: string
  • build?(ctx): void | Promise<void>

BundlerProvider

  • name: string
  • build(context): void | Promise<void>

Safety notes

For third-party compatibility:

  • keep optimization conservative by default
  • avoid blanket side-effect stripping of external packages
  • validate with smoke tests (build -> start -> endpoint checks)

Repository

  • https://github.com/manic-js/bundler