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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@tralse/developer-logs

v1.2.0

Published

Log kits that aid developers.

Downloads

5

Readme

developer-logs

A Node.js utility method for logging with environment-based states and colorful output. This utility allows tralse developers to log messages in different colors and formats based on the current environment configuration.

Features

  • Log messages in different colors:
    • blue,
    • green,
    • red,
    • magenta,
    • yellow,
    • cyan,
    • white,
    • black,
    • brightBlue,
    • brightGreen,
    • brightRed,
    • brightMagenta,
    • brightYellow,
    • brightCyan,
    • brightWhite, and
    • brightBlack.
  • Conditional logging based on environment variables.

Installation

To install the package, you can use npm:

npm install @tralse/developer-logs

Usage

Setup Environment Variables

Ensure you have a .env file in your project root with the following content:

  • If you are in development mode
NODE_ENV=development
  • If you are in debug mode
NODE_ENV=development
DEV_MODE=debug
  • If you are in production mode
NODE_ENV=production

Usage of Logger

Here's how to use logger.

import dotenv from "dotenv";
import { log } from "@tralse/developer-logs";

dotenv.config();

// Note that these logs can be printed when the process.env.NODE_ENV is set up to `development`.

// Logs in blue, and uses default header.
log.blue("This is a blue message");

// Logs in green, and uses header CustomHeader
log.green("This is a green message", "CustomHeader");

// Logs in red with a header CustomHeader, but only executes when DEV_MODE is set to debug.
log.red("This is a red message", "CustomHeader", "DEBUGMODE");

// Logs in magenta, uses default header.
log.magenta("This is a magenta message");

Contributing

Contributions are welcome! Please open an issue or submit a pull request for any changes.

License

This project is licensed under the MIT License.