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

ezcodin-logger

v1.0.9

Published

Simple logger

Downloads

9

Readme

EZCODIN-LOGGER

This is a very simple logger, that will allow you to console color coded debug statements, in addition to writing to log files. Currently three files are created info, warning, and error. Will be adding features over time.

Collaboraters welcome, looking forward to some pull requests!

VISIT: HOME PAGE

image

Install

> npm install ezcodin-logger

Setup

No Options:
const Log = require('ezcodin-logger')

//without callback or Options
let log = new Log()
With Callback:
const Log = require('ezcodin-logger')

//Optional Callback
let log = new Log( result => console.log(result))
With Options Object:
const Log = require('ezcodin-logger')

//Optional Options Object
let options = {
     colors:{
        error: 'red',
        warning: 'yellow',
        info: 'blue'
    },
    filePaths: {
        error: './logs/ez.error.log',
        warning: './logs/ez.warning.log',
        info: './logs/ez.info.log'
    }

}
let log = new Log( options)
All of the above:
const Log = require('ezcodin-logger')

//Optional Options Object
let options = {
     colors:{
        error: 'red',
        warning: 'yellow',
        info: 'blue'
    },
    filePaths: {
        error: './logs/ez.error.log',
        warning: './logs/ez.warning.log',
        info: './logs/ez.info.log'
    }

}

//With Options object and Callback
let log = new Log( options, result => console.log(result.msg)) //console => 'ezcodin-logger initialized'
# available colors: 
'black', 'red', 'green', 'yellow', 'blue', 'magenta', 'cyan', 'white', 'gray', 'redBright',
'greenBright', 'yellowBright', 'blueBright', 'magentaBright', 'cyanBright', 'whiteBright'

Log to Console

//debug logger
log.debugError('debug error')
log.debugWarning('debug warning')
log.debugInfo('debug info')

alt text

Log to File

Log files are created in the root directory automatically upon instantiating the logger, use the options object to place logs in another location.

//Log to file
log.logError('log error')
log.logWarning('log warning')
log.logInfo('log info')

alt text

Express example

app.use(function (req, res, next) {
    let err = new Error(`${req.ip} tried to reach ${req.originalUrl}, resource not found`);
    err.statusCode = 404;
    log.logInfo(err.statusCode + err.message )
    res.status(err.statusCode).json({ status: err.statusCode, msg: err.message });
}); 

app.use(function(err, req, res, next) {
    if (!err.statusCode) err.statusCode = 500;   
    log.logError(err.statusCode + err.message )
    res.status(err.statusCode).json({ status: err.statusCode, msg: err.message }); 
    }
});