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

@kilog/vite-plugin

v1.3.1

Published

Vite plugin for kilog structured logging

Downloads

526

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mr-akamimr-akami

Keywords

kilogloggingvitevite-plugin

Readme

@kilog/vite-plugin

Vite plugin. Injects the browser-side instrumentation script into index.html and registers a dev-server middleware that receives events and writes them to .kilog/.

Usage

// vite.config.ts
import { defineConfig } from "vite";
import kilogPlugin from "@kilog/vite-plugin";

export default defineConfig({
  plugins: [kilogPlugin()],
});

Running vite is enough to collect the browser's console, fetch, and uncaught errors.

Options

kilogPlugin({ terminal: true }); // mirror every captured event to stdout (colored)
kilogPlugin({ terminal: "warn" }); // only warn/error (filter by level)
kilogPlugin({ terminal: "error" }); // errors only
// default: no terminal output; events go to .kilog/ only

kilogPlugin({ persist: true }); // keep previous logs across dev restarts
// default: wipe .kilog/raw/*.jsonl and .kilog/index/ on server start

kilogPlugin({ server: false }); // disable server-side (Node/Bun/Deno) capture
// default: server capture is ON

The level threshold applies to events with a level (console, error, rejection). Network events print only when terminal: true.

Server-side capture (Vite SSR / Hono+Vite / Vite-Next)

When Vite bundles and runs your server code in its own Node process (e.g. via @hono/vite-dev-server, or any Vite-SSR setup), the plugin also instruments that process so console / fetch / uncaught errors from your server code land in .kilog/raw/{date}.{node|bun|deno}.jsonl — separated from browser events which go to .browser.jsonl.

This is enabled by default. Pass server: false to skip it (useful for pure-SPA projects):

kilogPlugin({ server: false });

Runtime detection (node / bun / deno) is handled by @kilog/register, which the plugin loads on dev server start.

How it works

  • transformIndexHtml: injects the browser instrumentation script into <head>
  • configureServer:
    • adds a POST-receiver middleware to the dev server (browser → dev server → .kilog/raw/)
    • when server !== false, dynamically imports @kilog/register so the dev-server runtime captures its own console / fetch / errors

Storage

Written to .kilog/raw/{date}.browser.jsonl under the cwd. Override with the KILOG_DIR environment variable.

Requirements

  • Vite 6 or newer (peerDependencies)
  • Dev server only — the instrumentation script is not included in production builds

Viewing logs

Use @kilog/cli or the Web UI.