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

@cyca/log

v0.1.1

Published

A simple logging library

Readme

@cyca/log

License: MIT

A lightweight, feature-rich logging library for JavaScript/TypeScript applications that works seamlessly in both browser and Node.js environments.

Features

  • 🎨 Colored console output with Unicode symbols
  • 📱 Dual environment support - Browser (localStorage) and Server (memory)
  • 🔧 Configurable log levels with persistent storage
  • 🏗️ Hierarchical loggers with named instances
  • 🎛️ Custom console implementations
  • 📦 TypeScript support with full type definitions
  • 🚀 Modern ES modules with tree-shakeable exports

Installation

npm install @cyca/log
yarn add @cyca/log
pnpm add @cyca/log
bun add @cyca/log

Quick Start

Basic Usage

import { log } from '@cyca/log';

// Simple logging
log.info('Application started');
log.warn('This is a warning');
log.error('Something went wrong');

// Different environments automatically detected:
// - Browser: uses localStorage for persistence
// - Server: uses in-memory storage

Log Levels

The library supports six log levels:

  • trace - Most verbose, typically for debugging
  • debug - Debug information
  • info - General information (default)
  • warn - Warning messages
  • error - Error messages
  • silent - Disable all logging
import { log } from '@cyca/log';

log.trace('Detailed debugging info');
log.debug('Debug information');
log.info('General information');
log.warn('Warning message');
log.error('Error message');

// Set minimum log level
log.setLevel('warn');

Named Loggers

Create hierarchical loggers for different parts of your application:

import { log } from '@cyca/log';

const apiLogger = log.getLogger('api');
const dbLogger = log.getLogger('database');
const authLogger = log.getLogger('auth');

// Different loggers can have different levels
apiLogger.setLevel('debug');
dbLogger.setLevel('error');

// Usage
apiLogger.debug('API request received');
dbLogger.error('Database connection failed');
authLogger.info('User authenticated');

Persistent Log Levels

Log levels are automatically persisted:

import { log } from '@cyca/log';

// Set log level (persisted across sessions)
log.setLevel('error');

// Reset to default
log.resetLevel();

// Set default level (only if no stored level exists)
log.setDefaultLevel('info');

Custom Console Implementation

Use a custom console implementation:

import { log } from '@cyca/log';
import electronLog from 'electron-log/renderer';

log.use(electronLog);

Advanced Usage

TypeScript Support

Full TypeScript definitions are included:

import { log, Logger, LogLevel, LoggerInstance } from '@cyca/log';

const logger: LoggerInstance = log.getLogger('myModule');

// Logger instances extend the standard Console interface
logger.assert(condition, message);
logger.clear();
logger.table(data);

Environment Detection

The library automatically detects the environment:

  • Browser: Uses localStorage for persistence and CSS-styled console output
  • Node.js: Uses in-memory storage and ANSI color codes

API Reference

Main Exports

  • log - Default logger instance
  • Logger - Main logger class
  • LogLevel - Log level type
  • LoggerInstance - Logger instance type
  • IStorage - Storage interface
  • LoggerOptions - Logger configuration options

Logger Methods

class Logger {
  // Log methods (automatically bound based on level)
  trace(...args: any[]): void
  debug(...args: any[]): void
  info(...args: any[]): void
  warn(...args: any[]): void
  error(...args: any[]): void

  // Level management
  setLevel(level: LogLevel): this
  setDefaultLevel(level: LogLevel): this
  resetLevel(): this

  // Logger management
  getLogger(name: string | symbol): LoggerInstance
  getLoggers(): Record<string, LoggerInstance>

  // Console management
  use(consoleImpl: Console): void
}

License

MIT © Cyrus Venn Casada

Contributing

Contributions are welcome! Please feel free to submit issues and pull requests.