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

log-rank

v1.0.7

Published

A priority-based console logger for Node.js and browser environments. Log messages with custom priorities and control the order they appear — ideal for debugging complex flows, batching logs, or building clean dev tools.

Readme

log-rank

A customizable console log utility with priority handling, message grouping, and emoji support.

📦 Installation

npm install log-rank

or

yarn add log-rank

💡 Why this package?

While working on a large codebase filled with scattered console.log() statements, filtering relevant logs became difficult. I built log-rank to give structure, priority, and clarity to console outputs—especially during debugging and feature development.


🚀 Features

  • Set priority for your console messages
  • Supports log, warn, error, success, and failure message types
  • Automatically clears console before reprinting grouped messages
  • Emoji support for success and failure logs
  • Toggle timestamps
  • Control max number of messages
  • Disable console globally if needed

📘 Usage

1. Basic Setup

import { Console } from "log-rank";

const logger = new Console({
  maximumConsoleAllowed: 100,
  isConsoleDisable: false,
  timeFormat: "ISO", // or "LOCALE"
  reversePriority: false,
  showTimestamps: true,
});

2. Log Types

Log

logger.log("This is a log message", { priority: 1, showTimestamps: false });

Warn

logger.warn("This is a warning", { priority: 2 });

Error

logger.error("This is an error", { priority: 3 });

Success

logger.success("Data saved successfully", "🎉", { priority: 1 });

Failure

logger.failure("Operation failed", "💥", { priority: 1 });

3. Flush the Console Queue

logger.flush();

⚙️ Configuration Options

Console constructor options

| Option | Type | Required | Default | Description | | ----------------------- | --------------------- | -------- | ------- | ----------------------------------------- | | maximumConsoleAllowed | number | ✅ | — | Max messages allowed before stopping logs | | isConsoleDisable | boolean | ❌ | false | Globally disable logging | | timeFormat | "ISO" | "LOCALE" | ✅ | — | Format of timestamps | | reversePriority | boolean | ❌ | false | Show low priority messages first |

Logging Options

Each log method (log, warn, error, success, failure) accepts:

{
  priority?: number;        // Optional priority level (default: 1)
  showTimestamps?: boolean; // Whether to show timestamp (default: false)
}

📦 Example Output

✅ 2025-04-14T12:00:00.000Z:
Data saved successfully

❌ 2025-04-14T12:01:00.000Z:
Operation failed

2025-04-14T12:02:00.000Z:
This is a log message

🙌 Contribution

Pull requests and feature suggestions are welcome!


📝 License

MIT License


Built with ❤️ to clean up your console mess!