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

nubo-logger

v3.6.9

Published

A colorful console logger utility for development

Readme

🌈 Nubo Logger

A beautiful, colorful console logger utility for TypeScript/JavaScript development that makes debugging enjoyable!

npm version License: MIT TypeScript

✨ Features

  • 🎨 Provides multiple color options for better log visualization.
  • 🧠 Includes full TypeScript support with type definitions.
  • ⚡ Has zero dependencies, making it lightweight and fast.
  • 🌍 Automatically disables logging in production environments.
  • 🔧 Offers a simple and easy-to-use API.
  • 🔁 Supports both ESM and CommonJS module systems.

📦 Installation

npm install nubo-logger
# or
yarn add nubo-logger
# or
pnpm add nubo-logger
# or
bun add nubo-logger

🚀 Usage

Basic Usage

import log from "nubo-logger";

// log.t adds a timestamp to the output
// log.b makes the output bold
// log.t.b applies both timestamp and bold formatting

log.t.mint("[scope]", "This is a mint message with additional description");
log.mint("[scope]");
log.t.mint("[scope] with time");
log.b.mint("[scope]", "All string in bold");
log.t.b.mint("[scope]", "All string in bold", "ISOString + bold");

Advanced Usage

import { NuboLogger } from "nubo-logger";

const logger = new NuboLogger({ enableInProduction: true });

logger.b.mint("[scope-2]", "This is a mint message with additional description");
logger.t.indigo("[scope-2]", "This is an indigo debug message with ISOString");
logger.cyan("[scope-2]", "@cyan", "Scope");

🎨 Available Colors

| Method | Color | Use Case | |-------------|----------|-------------------------------| | blue() | 🔵 Blue | Information, links | | brown() | 🟤 Brown | Logs related to storage/files | | cyan() | 🔷 Cyan | Highlights, emphasis | | gray() | ⚫ Gray | Less important info | | gray2() | ⚫ Gray2 | Slightly darker info | | gray3() | ⚫ Gray3 | Darker muted info | | gray4() | ⚫ Gray4 | Even darker info | | gray5() | ⚫ Gray5 | Near-black info | | gray6() | ⚫ Gray6 | Background black | | green() | 🟢 Green | Success, completion | | indigo() | 🟣 Indigo| Accents, strong debug | | label() | ⚪ Label | Bright white foreground | | mint() | 🟢 Mint | Fresh, success with emphasis | | orange() | 🟠 Orange| Warnings, important notes | | pink() | 🌸 Pink | Friendly or soft emphasis | | purple() | 🟣 Purple| Debug, special notes | | red() | 🔴 Red | Errors, critical issues | | teal() | 🟦 Teal | Calm or balanced output | | yellow() | 🟡 Yellow| Warnings, attention |

📊 Log Levels

| Method | Level | Description | Example Usage | |-----------|---------|-------------------------------|--------------------------------------------| | error() | Error | Critical errors and exceptions| log.error("Critical failure:", error); | | warn() | Warning | Warning messages | log.warn("Deprecated API usage."); | | info() | Info | General information | log.info("User logged in successfully.");| | debug() | Debug | Debug information | log.debug("Fetching user data:", userId);|

⚙ Configuration

interface NuboLoggerOptions {
  enableInProduction?: boolean; // Optional, default: false
}

// Default configuration disables logging in production
const defaultLogger = new NuboLogger();

// Custom configuration to enable logging in production
const logger = new NuboLogger({
  enableInProduction: true,
});

🌍 Environment Behavior

  • In non-production environments (NODE_ENV !== 'production'): All logs are displayed.
  • In production environments (NODE_ENV === 'production'): Logs are suppressed by default.
  • Override production suppression by passing enableInProduction: true to show logs.

🧪 Examples

Error Handling

try {
  logger.green('Operation completed successfully.');
} catch (error) {
  logger.red('Operation failed:', error.message);
}

API Responses

const response = await fetch('/api/data');

if (response.ok) {
  logger.green(`API call successful: ${response.status}`);
} else {
  logger.red(`API call failed: ${response.status}`);
}

Debug Information

logger.cyan('Debugging user flow:');
logger.blue(`Timestamp: ${new Date().toISOString()}`);

🧪 Testing

npm test
npm run test:watch
npm run test:coverage

Note: npm run test:coverage will fail if coverage thresholds are not met. Adjust thresholds in jest.config.js as needed.

🛠 Development

$ npm install

$ npm run dev

$ npm run build

$ npm run lint

$ npm run format

📄 License

MIT © 3v69

🙌 Contributing

Contributions, issues, and feature requests are welcome! Please see CONTRIBUTING.md for guidelines.

  1. Fork the project
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

📈 Stats

GitHub stars GitHub forks GitHub issues


❤️ Made with love by 3v69