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

kunsul

v0.0.5

Published

Debug logging utility that is ignored by default in production builds

Downloads

38

Readme

Kunsul 📝

A simple logging utility wrapper that will be ignored by build tools (vite, webpack, etc) in production by toggling the KUNSUL_IGNORE_IN_BUILD constant.

NOTE

  • ESM works best in tree shaking/dead code elimination so I recommend to always use it
  • when you use import it will automatically choose ESM

How It Works ⚙️

  • In development, set KUNSUL_IGNORE_IN_BUILD = false to always show logs or dont set anything(by default it will always show logs).
  • In production, set KUNSUL_IGNORE_IN_BUILD = true and build tools (like Webpack, Vite, Rollup, etc.) can eliminate logging calls during tree-shaking/minification.
  • This way, you keep helpful logs while developing without shipping them into production bundles.

see examples to see how to integrate in build-tools

Installation

npm install kunsul 

or

npm install kunsul --save-dev

Usage


// for esm
// best for tree shaking/dead code elimination
globalThis.KUNSUL_IGNORE_IN_BUILD = true; // build-tools will ignore kunsul and will not include it in build-output
import kunsul from "kunsul"
kunsul.log("hello, world")




// for cjs
// although the logs wont show, the kunsul functions will still be in the build output due to cjs is not best for tree shaking in build-tools
globalThis.KUNSUL_IGNORE_IN_BUILD = true; // you can toggle this in your build tool by default kunsul shows all logs
const kunsul = require('kunsul');
kunsul.log('CommonJS log test');

CURRENT WORKING/ACTIVE kunsul API'S

  kunsul.log,
  kunsul.info,
  kunsul.debug,
  kunsul.warn,
  kunsul.error,
  kunsul.group,
  kunsul.groupEnd,
  kunsul.groupCollapsed,
  kunsul.table,
  kunsul.time,
  kunsul.timeEnd,
  kunsul.count,
  kunsul.countReset,
  kunsul.trace,
  kunsul.assert,
  kunsul.clear,
  kunsul.json,
  kunsul.createLogger,

Plans

  • expand logging capabilities
    • fetch: fetchWithLog,
    • maybe add kunsul.prod but still debating if its usefull since you can just do console.log....
    • .......
  • add more examples