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

winston-decorator

v0.0.8

Published

A decorator version of the winston logger written completely in Typescript.

Downloads

232

Readme

Winston Decorator

npm npm version Build Status codecov Dependencies license

A decorator version of the winston logger written completely in Typescript.

Installation

npm install winston-decorator

Usage

winston-decorator is designed to inject a winston logger on the decorated property of the given class.

For example:

import {logger, LoggerInstance} from 'winston-decorator'

class Test
{
    @logger()
    private _logger;
    
    public constructor()
    {
        this._logger.info('Now I can use the logger from here!');
    }
}

You can pass a winston.LoggerOptions object to the decorator to specify your settings:

@logger({level: 'debug'})

or you can put it on a separate settings file if you prefer to change the settings of all your loggers at once.

import settings from './settings'
class Test
{
    @logger(settings)
    private _logger;
    
    public constructor()
    {
        this._logger.info('Now I can use the logger from here!');
    }
}

The logger comes with a default label set on your class name so you can always know from where your log come from. For example:

verbose: [APIServer] Route loaded successfully
debug: [Route] Function called
verbose: [APIServer] Route loaded successfully
info: [APIServer] Listening on port 8080!

but you can change it if you want, setting it on the decorator

import settings from './settings'
class Test
{
    @logger(settings, {label: 'test'})
    private _logger;
    
    public constructor()
    {
        this._logger.info('This will output <[test] ...>');
    }
}

Test environment

The logger is designed to automatically hide all the logs when testing environment is set. To do so you have to set the process.env[NODE_ENV] variable to "test" (like this: NODE_ENV=test node main.js). But you can also opt for a custom value for the env_variable. To specify it just pass it to the decorator settings.

import settings from './settings'

class Test
{
    @logger(settings, {test_environment: 'my_custom_env'})
    private _logger;
    
    public constructor()
    {
        this._logger.info('This will be hidden');
    }
}

In this case you can run the program with NODE_ENV=my_custom_env mocha test.js and hide all the logs from the output.

Run tests

npm test

Authors

Marco Moschettini, Alessandro Petraro