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

@yucom/logger

v0.2.0

Published

Preconfigured event logger

Downloads

6

Readme

Alfa-Logger

Preconfigured logger for most uses.

How to use

Set Up

npm install @yucom/logger --save

First of all, set where to log to.

    const Logger = require('@yucom/logger')
    Logger.logTo("/path/to/log")

Valid values are "console", "stdout" (synonym of "console"), "docker" (currently uses stdout) and a path to a folder.

If a folder is specified, when in production mode (environment variable NODE_ENV has value production) folder is created if not exist and log files are created there. Files are rotated dialy and old files are conserved for 5 days and finally deleted. When not in production environment, logs to the console, ignoring the folder. Log level is also preconfigured based on environment. In production, only error and warn are logged. When not in production, all levels are shown.

If @yucom/context is installed, variable txid is included in log

Begin To Write

In your program files, just write:

    const Logger = require('@yucom/logger')
    
    Logger.debug("This is my first message")
    //[2018-11-22T04:08:55.017Z] DEBUG: This is my first message
    
    Logger.error("This is my first error")
    //[2018-11-22T04:09:55.017Z] ERROR: This is my first error
    
    try {
        (null).jump()  //
    } catch(err) {
        Logger.error(err)
    }
    //[2018-11-22T04:22:19.249Z] ERROR: TypeError: Cannot read property 'jump' of null

Available methods/levels, sorted from less to more important are:

  • silly
  • debug
  • verbose
  • info
  • warn
  • error

All of then takes any as argument.

Scoped Loggers

In previous examples a global logger is used. In practice, it is recommended to do all your stuff with a scoped logger. A scoped logger is exactly like the global logger but it's created with a label which is shown at the begining of every message.

    //Notice the scope as an argument at the end of this line
    const Logger = require('@yucom/logger')('my-module')
    
    Logger.debug("This is my first message")
    //[2018-11-22T04:08:55.017Z][my-module] DEBUG: This is my first message
    //                           ^--- Here it is!