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

@jackdbd/tags-logger

v1.1.0

Published

A logger inspired by how logging is implemented in Hapi.js.

Downloads

3

Readme

@jackdbd/tags-logger

npm version Snyk Vulnerabilities for npm package

A logger inspired by how logging is implemented in Hapi.js.

Features

  • tags to pinpoint the log statements you are actually interested in.
  • optional validation of all log statements with Joi.
  • easy switching bewteen structured/unstructured logging.

Installation

npm install @jackdbd/tags-logger

Usage

structured logging

When you write this:

import makeLog from '@jackdbd/tags-logger'

const log = makeLog()

log({
  message: 'something not very important about foo and bar',
  tags: ['debug', 'foo', 'bar']
})

log({
  message: 'something of critical importance about baz',
  tags: ['critical', 'baz']
})

You get this:

{
  "severity": "DEBUG",
  "message": "something not very important about foo and bar",
  "tags": ["bar", "foo"],
  "tag": {"bar": true, "foo": true}
}

{
  "severity": "CRITICAL",
  "message": "something of critical importance about baz",
  "tags": ["baz"],
  "tag": {"baz": true}
}

unstructured logging

When you write this:

import makeLog from '@jackdbd/tags-logger'

const log = makeLog({
  namespace: 'my-app/my-module'
})

// same log statements as above

You get this (but with colors):

my-app/my-module [🔍 bar,foo] something not very important about foo and bar +0ms

my-app/my-module [🔥 baz] something of critical importance about baz +0ms

Don't like emojis? Then write this:

import makeLog from '@jackdbd/tags-logger'

const log = makeLog({
  namespace: 'my-app/my-module',
  should_use_emoji_for_severity: false // <--
})

// same log statements as above

And get this (but with colors):

my-app/my-module [debug bar,foo] something not very important about foo and bar +0ms

my-app/my-module [critical baz] something of critical importance about baz +0ms

Configuration

Environment variables

| Environment variable | Explanation | | --- | --- | | DEBUG | You must set this environment variable if you want to use unstructured logging and see some output. This library delegates unstructured logging to debug.

Options

| Option | Default | Explanation | | --- | --- | --- | | namespace | undefined | The namespace for unstructured logging. This option has no effect when using structured logging. | | should_use_emoji_for_severity | true | Whether to use an emoji for the severity level, when using unstructured logging. This option has no effect when using structured logging. | | should_validate_log_statements | false when process.env.NODE_ENV === 'production'. Otherwise true | Whether each log statement should be validated against a Joi schema. |

API

API docs generated with TypeDoc