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

@kaehehehe/visual-console

v2.0.1

Published

A lightweight and customizable console logging library that enhances your developer experience by adding stylish, themeable, and emoji-supported visual logs. Perfect for debugging with clarity and flair.

Readme

@kaehehehe/visual-console 🐰✨

Styled console logs made simple — a cute visual wrapper for your console logging with fun themes and emojis! 🎉

Features 🌈

  • Pretty themed logs: info, success, warn, error
  • Easy custom styles for your logs
  • Simple API for quick & delightful debugging

Installation 🚀

npm install @kaehehehe/visual-console
# or
yarn add @kaehehehe/visual-console
# or
pnpm add @kaehehehe/visual-console

Usage 🎨

import vc from "@kaehehehe/visual-console"

// Logs with theme
vc.log("✅ Success log!", { theme: "success" });
vc.info("💡 Info log!", { theme: "info" });
vc.warn("⚠️ Warning log!", { theme: "warn" });
vc.error("🚨 Error log!", { theme: "error" });

스크린샷 2025-05-29 11 29 03

// Custom colorful log 💜
vc.log("Custom styled log 💖", {
  style: {
    color: "#FF00FF",
    background: "#FFF0FF",
    padding: "5px 10px",
    borderRadius: "5px",
  },
});

스크린샷 2025-05-29 11 45 11

API Summary 📚

| Method | What it does | Params | | ---------------- | ------------------------ | ---------------------------------------------------------------------- | | log | Basic log | (text: string, options?: { theme?: LogLevel, style?: ConsoleStyle }) | | info | Info level log | (text: string, options?: { theme?: LogLevel, style?: ConsoleStyle }) | | warn | Warning level log | (text: string, options?: { theme?: LogLevel, style?: ConsoleStyle }) | | error | Error level log | (text: string, options?: { theme?: LogLevel, style?: ConsoleStyle }) | | assert | Conditional assert log | (text: string, options?: { theme?: LogLevel, style?: ConsoleStyle }) | | group | Start a group in console | (text: string, options?: { theme?: LogLevel, style?: ConsoleStyle }) | | groupCollapsed | Start a collapsed group | (text: string, options?: { theme?: LogLevel, style?: ConsoleStyle }) |

Important Notice for Production Builds ⚠️

  • This library uses process.env.NODE_ENV to detect the environment and disable console logs in production.
  • Make sure your build tool (e.g., Vite, Webpack, etc.) properly sets process.env.NODE_ENV to "production" when creating production bundles.
  • If NODE_ENV is not set correctly, console logs may still appear in your production code.
  • Most modern bundlers automatically handle this, but double-check your build configuration to ensure dead code elimination works as expected.
  • For best results, run your production build command with environment variables properly configured, for example:
NODE_ENV=production vite build