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

trussle-logging

v1.1.8

Published

A simple logging library by Trussle, that one day will more than likely become an overcomplicated beast

Downloads

322

Readme

trussle-logging


A simple library for all things logging.


##Simplest Usage

var log = require("trussle-logging")("MyComponent");

If you are going for the simplest usage you will need to set the NODE_LOG_LEVEL Environment Variable


export NODE_LOG_LEVEL=DEBUG

##Advanced Usage

If you are going for some advanced usage you there are several options

{
  source: "ComponentName", // Name for component useful for navigating to your js file
  transport: new TransportClass(), // Logging transport can also be an array, default is console transport
  level: "INFO", //See log sevels, if not set the the NODE_LOG_LEVEL environment will be used.
  formatter: (logData) => `${logData.message}` //See Formatters
}

###Log Levels

  • TRACE
  • DEBUG
  • INFO
  • WARN
  • ERROR
  • CRITICAL
  • NONE

###Transports

The default Transport logs to the console. If you want to write to own trasport then it will have to comply with the following interface.

{
  trace(message),
  debug(message),
  info(message),
  warn(message),
  error(message),
  critical(message)
}

###Templates

Templates are functions that take a logData object and return the output to be sent to the transport.

The logData Object has these properies

{
  timestamp, // A moment object of the current utc time
  source, // The source component of the log
  level, //The log level
  message // The original log message
}

For more info on moment objects check out momentjs

If no formatter is chosen then the default will be chosen.


(logData) => `(${logData.source}) [${logData.level}] ${logData.message}`;

###Multiple Logs

If your usecase requires you to have multiple logs seperate log files for INFO and ERROR logs for instance (only the ConsoleTransport at this time so if you need to log to a file you'll need to roll your own transport class) then you can add a variants property to your config, this will create a wrapper logger that will delegate to multiple loggers.

{
  source: "ComponentName",
  level: "INFO",
  variants: [
    {
      level: "ERROR",
      transport: new MyCustomTransport()
    }
  ]
}