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

log-stdout

v1.1.2

Published

Logger for Node.js using console.log() only

Downloads

5

Readme

log-stdout

A JavaScript logging module for Node.js that logs by calling console.log(). Intended to be used together with other tools (e.g. docker) that grab lines written to stdout and add their own stuff such as timestamps.

Installation

npm install log-stdout

Usage

Create a log object when your application starts:

// logger.js
const createLogger = require("log-stdout");

const logger = createLogger(process.env.LOG_LEVEL || "debug");

module.exports = logger;

Use the logger:

// index.js
const logger = require("./logger");

// Log some string using the "info" log level
logger.info("Some string");
// Output:
// info: Some string

// Log a couple of strings and numbers using the "error" log level
logger.error("Some string", 7, "also a string", 8);
// Output:
// error: Some string 7 also a string 8

// Log an error using the "error" log level
logger.error(new Error("An error happened"));
// Output:
// error: An error happened<stack trace>

// Log some string and an error using the "debug" log level
logger.debug("Some string", new Error("An error happened"));
// Output:
// debug: Some string Error: An error happened<stack trace>

// Log some string, an error and more stuff using the "warn" log level
logger.warn("Some string", new Error("An error happened"), "more", {
  stuff: "stuff"
});
// Output:
// warn: Some string Error: An error happened<stack trace> more { stuff: 'stuff'}

Valid log levels

You can pass one of the following log levels to the function that is returned by require("log-stdout") (which is createLogger() in the above example):

  • silent
  • error
  • warn
  • info
  • debug

The return value of the function returned by require("log-stdout") is an object that has a method for each log level except "silent". Each of these methods has the same name as the corresponding log level. Calling any of these methods will either result in log output or not depending on the log level the logger was created with.

Log output

The output of any of the log methods (e.g. logger.debug("some message")) is a string that has only a single line. Inside that string, line breaks are written as \n.