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

buner

v1.0.12

Published

Frontend build toolkit for Vite + React SSR projects — SCSS pipeline, prerender, SSR dev server, and backend integration.

Readme

buner

Frontend build toolkit for Vite + React SSR projects — SCSS pipeline, SSR dev server, prerender, and backend integration.

Install

npm install buner

Or install globally for the CLI:

npm install -g buner

Quick Start

Scaffold a new project

npx buner create my-app
cd my-app

buner create now asks you to choose a package manager (npm, pnpm, yarn, or bun) and installs dependencies automatically.

Development

npx buner dev

Starts all watchers concurrently: SCSS, states, Vite HMR, and the Express SSR dev server.

Production Build

npx buner build

Produces dist/static/ (client) and dist/server/ (SSR) output.

Static Site Generation

npx buner generate

Runs: states → styles → build → prerender (with content hashes).

Build for Deployment (eshn mode)

npx buner eshn

Same as generate but with --mode eshn.

Backend Integration

npx buner inte

Runs: styles → build → prerender → copies assets to the directory configured in VITE_INTE_ASSET_DIR (set in .env).

CLI Commands

| Command | Description | | -------------------- | ---------------------------------------------------- | | buner create [dir] | Scaffold a new frontend project | | buner dev | Watch mode (styles + states + Vite HMR + SSR server) | | buner serve | Start the SSR dev server only | | buner build | Vite static + SSR build | | buner generate | Full static site generation | | buner eshn | Generate with --mode eshn | | buner inte | Build and integrate with backend | | buner styles | Compile SCSS only | | buner prerender | Pre-render HTML files only |

Configuration

Configuration is done via .env files in your project root:

| Variable | Default | Description | | ----------------------- | --------- | ------------------------------------------------------------------- | | VITE_BASE_URL | / | Base path for all assets | | VITE_PORT | 5000 | Dev server port | | VITE_PATH_EXTENSION | '.html' | File extension for routes (.html or empty) | | VITE_TITLE_SUFFIX | — | Browser tab title suffix | | VITE_INTE_ASSET_DIR | — | Integration output path for assets (e.g. ../MyApp/wwwroot/assets) | | VITE_INTE_PATTERN_DIR | — | Integration output path for HTML patterns |

Override per environment with .env.development, .env.eshn, etc.

Peer Dependencies

Your project must install these:

npm install react react-dom react-router-dom

Project Structure

A buner project looks like this:

my-app/
├── .env                    # Environment variables
├── index.html              # HTML template
├── vite.config.ts          # Vite config (imports buner's xpack/config)
├── tsconfig.json
├── public/
│   └── assets/             # Static assets (fonts, images, vendors)
└── src/
    ├── app.tsx             # Route definitions → components
    ├── entry-client.tsx    # Client-side hydration
    ├── entry-server.tsx    # SSR render function
    ├── routes.ts           # Route registry
    ├── react-loader.tsx    # Lazy component loader
    ├── pages/              # Your page components
    ├── atoms/              # Atomic components
    ├── molecules/          # Molecular components
    ├── organisms/          # Organism components
    └── assets/
        ├── styles/         # SCSS (abstracts, mixins, base)
        └── scripts/        # Standalone JS/TS assets

SCSS Pipeline

buner compiles SCSS with sass + postcss + autoprefixer + cssnano.

SCSS files are automatically discovered from:

  • src/assets/styles/style-base.scss — base styles (includes atoms + molecules)
  • src/organisms/**/*.scss — prefixed with b-
  • src/templates/**/*.scss — prefixed with p-
  • xpack/styles/**/*.scss — framework UI styles

SCSS Migration

To replace deprecated @import statements with @use and @forward:

bun migrate-scss.ts

License

MIT