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

loggnog

v1.1.0

Published

An opinionated, lightweight logger for AWS-hosted TypeScript apps

Downloads

20

Readme

loggnog

loggnog is a lightweight logging library for Node.js, designed to print your logs as clear and color-coded as possible both in AWS CloudWatch and in your local terminal.

Why

I have been using winston, a great and versatile module and pretty customizable. But from some point it made more sense to me to create a lightweight alternative customized just for my local + AWS logging needs rather than to keep tweaking winston.

Key features

  • The module will print nicely formatted logs both in local and AWS environments (given isAws is configured dynamically to be truthy in an AWS environment only). That includes environment-appropriate color coding of object keys and values, as well as the capability to view JSON objects in with human-readable indentation.

  • Since AWS logs are JSON objects, it is impossible to color strings there, so I am using little emoji squares and triangles to add a little color-coding.

  • Following log methods are available:

    1. error
    2. problem
    3. warn
    4. info
    5. debug
  • debug level logs may be prevented from getting logged if isDebugMode is falsy

  • The introduction of problem level logs aims to capture error responses resulting from certain API requests. These errors signify expected behavior on the server but may present as issues for the client. Typically, problem level logs correspond to HTTP status code 400, while error level logs are reserved for HTTP status code 500 responses.

Quick start

const { Loggnog } = require('loggnog');

// configure
const logx = new Loggnog({ isAws: true, isDebugMode: false });

// Log a message
logx.info('This is a log message');

// Debug message
// This message will be logged inly if isDebugMode is truthy above
logger.debug('FOO_PAYLOAD', { foo: 'bar' });

// Log an error
logx.error('OTHER_ERROR', new Error('Something went wrong'));

Configuration

| Key | Default | Description | | ----------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | isAws | false | Tell the module (programmatically) if it runs in the AWS environment to optimize for that environment. Optimized for local console by default | | isDebugMode | false | if true logx.debug messages will be logged to the terminal |

Limitations

  • Log methods can accept 1 or 2 arguments, and the first one must always be a regular string
  • Extremely opinionated, no room for customization
  • No equivalent for console.log, use logx.info instead