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 🙏

© 2025 – Pkg Stats / Ryan Hefner

chocolog

v1.1.3

Published

A highlighted android-style logger

Readme

Chocolog

A simple logger

Usage

import { cLog } from "chocolog"
// access directly
cLog.d("🤔")
// create instance with name
const log = cLog.getLogger("tsmap")
log.d("🤔")

Parameters length can be 1 or 2+

// content with default header(name)
cLog.d("🤔")
// content with custom header (first param)
cLog.d("thinking face", "🤔")
// multiple content (joining all) params with custom header
cLog.d("faces", "🤔", "🙃", "😗")

alt text

Parameters type can be anything (but recommend Serializable)

// primitive type
cLog.i("Primitives", 37, " ", true, " ", null)
// simple object
cLog.i("Object", {
    thinking: "🤔",
    upsideDown: "🙃",
})
// array
cLog.i(["LoLInsect", "Detected"])
// map
const mp = new Map<string, string>()
mp.set("Top", "Teemo")
mp.set("Mid", "Riven")
mp.set("ADCarry", "Ezreal")
cLog.i("Loading", mp)
// Error
cLog.i("Oops", new Error("Trolling"))
// Function.. (not correctly)
cLog.i("Fn", (str:string) => `Hello, ${str}!`)

param type

Logging API

cLog.v(title[, ...desc])

  • Verbose (~~336 Hue~~Follows default text color)
  • loglevel 1
  • Header V

cLog.d(title[, ...desc])

  • Debug (206 Hue)
  • loglevel 2
  • Header D

cLog.i(title[, ...desc])

  • Info (122 Hue)
  • loglevel 3
  • Header I

cLog.w(title[, ...desc])

  • Warning (35 Hue)
  • loglevel 4
  • Header W

cLog.e(title[, ...desc])

  • Error (4 Hue)
  • loglevel 5
  • Header E
  • Contents will be colored to red

cLog.wtf(title[, ...desc])

  • Assert (294 Hue)
  • loglevel 6
  • Header F

log bg

cLog.code(code[, title])

  • type code string
  • type title string | number | boolean
  • loglevel 1
  • Header C

Prints code using emphasize(highlight.js)

log code

Theme API

Used highlight.js styles from github, so preview and types are available to highlight.js repo.

cLog.setCssTheme(css)

  • type css css text

Set logger's color schema to css css. Class selector Prefix hljs requires to parsing.

async cLog.setStyleGithub(theme)

  • type theme highlight.js theme (name)

Set logger's color schema to theme. I used emphasize's sheet. Some theme may not supported.

Example

Call Origin (Experimental)

Due to some limitation to parse call origin, default is disabled to use call origin. Call origin can be enabled by passing CLOG_ORIGIN enviroment.

This modifies stacktrace much deeper globally! I haven't found the way detecting caller without extended stacktrace.

// launch.json
"env": {
    ...
    "CLOG_ORIGIN": "true"
}

And for typescript, It uses external sourcemap file to get infomation of .ts, so needs to export sourceMap as .map file.

// tsconfig.json
{
    ...
    "sourceMap": true
}