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

asijs-vite

v1.0.0

Published

Vite 8 / Rolldown dev server for AsiJS — run AsiJS API routes and Vite frontend on one port, with HMR bridge and Rolldown SSR builds

Readme

asijs-vite — Vite 8 / Rolldown dev server for AsiJS

Run an AsiJS backend and a Vite frontend on a single port. AsiJS handles API routes, Vite handles the frontend (HMR, transforms) — no proxy juggling, no two terminals.

Installation

bun add asijs-vite

Requires asijs and vite (>= 5; 8 / Rolldown supported) as peer dependencies.

Quick Start

// vite.config.ts
import { defineConfig } from "vite";
import { Asi } from "asijs";
import { createVitePlugin } from "asijs-vite";

const app = new Asi();
app.get("/api/hello", () => ({ message: "Hello from AsiJS!" }));

export default defineConfig({
  plugins: [createVitePlugin(app, { apiPrefix: "/api", hmrBridge: true })],
});
bun run dev   # Vite serves the frontend on 5173, /api/* goes to AsiJS

Or scaffold a full starter:

bunx asijs create my-app -t vite-app

API

| Export | Description | |--------|-------------| | createVitePlugin(app, opts?) | Vite plugin: wires the AsiJS middleware into configureServer / configurePreviewServer. | | createViteHandler(app, opts?) | Plain (request) => Response handler (Vite middleware mode / custom wiring). | | createViteMiddleware(app, opts?) | Connect-style middleware for server.middlewares.use(...) when wiring manually. | | attachHmrBridge(server, app, opts?) | Forward AsiJS hot-reload events to Vite's WebSocket (full-reload). | | ssrBuild(opts) | SSR bundle via Rolldown (Vite 8's bundler) when installed, falling back to Bun.build. |

Options (AsijsViteOptions)

| Option | Default | Description | |--------|---------|-------------| | apiPrefix | "/api" | Path prefix(es) routed to AsiJS; everything else falls through to Vite. | | stripPrefix | false | Strip the prefix before handing the request to AsiJS. | | hmrBridge | false | Watch AsiJS source and send full-reload to Vite clients on backend changes. | | watchDirs | ["src"] | Directories watched by the HMR bridge. | | verbose | false | Request / error logging. | | onError | 500 JSON | Custom error handler. |

ssrBuild

import { ssrBuild } from "asijs-vite";

const res = await ssrBuild({
  entry: "src/ssr.tsx",
  outDir: "dist-ssr",
  outFile: "index.js",
});
if (res.ok) console.log("SSR bundle at", res.outputPath, "via", res.engine);

Uses Rolldown (the bundler behind Vite 8) when it is installed, and falls back to Bun.build otherwise — res.engine reports which one ran.

How it works

createVitePlugin registers a Connect middleware at the front of Vite's middleware stack. Requests whose pathname matches apiPrefix are converted to a standard Request and passed to app.handle(); the Response is written back to the Node-style res. Everything else flows through to Vite's own middleware (HTML, modules, assets, HMR).

With hmrBridge: true, the plugin starts an AsiJS HotReloader over your source dir and pushes { type: "full-reload" } to Vite's WebSocket when backend handlers/routes change — the browser reloads without a manual refresh.

License

MIT