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

@richardpickett/logger

v1.0.3

Published

A library for console logging

Downloads

27

Readme

logger

Description

chalk-based logging for your log-reading pleasure

npm i @richardpickett/logger

Example:

// your own logger.js
import { Logger, defaultLabels } from "@richardpickett/logger";

// we only want to log these in our app
// ideally you'll use a config and build the flags from your config
// so you can have all the logging in your code and control what gets
// seen through your config file

const logThese = ["LOG", "INFO", "SUCCESS", "ERROR"];

const flags = {};

defaultLabels.forEach((label) => {
  flags[label] = logThese.indexOf(label) > -1;
});

const logger = new Logger({ flags });

export default logger;
// now in your project files:
import logger from "./logger.js";

logger.info("This is an info mesage");
logger.success("This is what success looks like");
logger.warning("This message should not get displayed");
logger.error("Looks like we have a problem, Houston");

Prefix

You can set a prefix on all your log entries by calling setPrefix():

logger.setPrefix(`[ProcessId: ${process.pid}]`);
logger.info("New worker started");
// yields: [2023-11-21T20:01:34Z] [INFO] [ProcessId: 45] New worker started

Additional constructor arguments

The full constructor parameter is a single object, defaulted like this:

{
    methods = [
      {
        label: "LOG",
        methodName: "log",
        consoleMethod: "log",
        labelChalk: standardColors.LOG_LABEL,
        textChalk: standardColors.LOG_TEXT,
      },
      {
        label: "DEBUG",
        methodName: "debug",
        consoleMethod: "log",
        labelChalk: standardColors.DEBUG_LABEL,
        textChalk: standardColors.DEBUG_TEXT,
      },
      {
        label: "INFO",
        methodName: "info",
        consoleMethod: "log",
        labelChalk: standardColors.INFO_LABEL,
        textChalk: standardColors.INFO_TEXT,
      },
      {
        label: "TRACE",
        methodName: "trace",
        consoleMethod: "log",
        labelChalk: standardColors.TRACE_LABEL,
        textChalk: standardColors.TRACE_TEXT,
      },
      {
        label: "SUCCESS",
        methodName: "success",
        consoleMethod: "log",
        labelChalk: standardColors.SUCCESS_LABEL,
        textChalk: standardColors.SUCCESS_TEXT,
      },
      {
        label: "WARNING",
        methodName: "warning",
        consoleMethod: "error",
        labelChalk: standardColors.WARNING_LABEL,
        textChalk: standardColors.WARNING_TEXT,
      },
      {
        label: "ERROR",
        methodName: "error",
        consoleMethod: "error",
        labelChalk: standardColors.ERROR_LABEL,
        textChalk: standardColors.ERROR_TEXT,
      },
    ],
    flags = { LOG: true, DEBUG: true, INFO: true, TRACE: true, SUCCESS: true, WARNING: true, ERROR: true },
    prefix = "",
    logDisabled = true,
  }

methods: these are the formats for all the logger.<method>() calls. Create your own, or override these to change the formatting.

flags: these turn methods on or off. If a flag is missing, it will default be turned off. Calling a method that is turned off will not result in an error, it's just not logged.

prefix: set this prefix to all your logs. This way you can create multiple logger instances and separate their logs from the output using the prefix

logDisabled: when the logger is initialized it will log all the disabled log methods. This by default will appear at the top of your log file, self-explaining why certain logs may not be seen.