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

@playo/logger

v0.9.24

Published

logger for playo

Downloads

375

Readme

Playo-logger

It will create logs winston according to services

It will delete logs before 30 days

PASS SERVER=production to skip debug logs

Log Levels

  1. alert (Highest Priority)
  2. error
  3. info
  4. debug

How to use

  1. Basic Logger create one logger file and add

    const PlayoLogger = require("@playo/logger");
    
    const Logger = new PlayoLogger("<service-name>");
    
    module.exports = Logger;

    It will create <service-name>-YYYY-MM-DD-info , <service-name>-YYYY-MM-DD-error, <service-name>-YYYY-MM-DD-debug file in /var/log/playo folder

  2. Store Logs in Different Path

    const PlayoLogger = require("@playo/logger");
    
    const Logger = new PlayoLogger("<service-name>", "<path-name>");
    
    module.exports = Logger;

    It will create <service-name>-YYYY-MM-DD-info , <service-name>-YYYY-MM-DD-error, <service-name>-YYYY-MM-DD-debug file in <path-name> folder

  3. Mail Logger

    const PlayoLogger = require("@playo/logger");
    
    const Logger = new PlayoLogger("<service-name>");
    Logger.setMailer({
      'receiverEmail': ["[email protected]"], // array of recievers, mandatory
      'senderEmail': "[email protected]" // address of sender, mandatory
      'senderName': 'Mail Logger' // default: Mail Logger, optional
      'replyEmail': '[email protected]' // default: [email protected], optional
      'region': "us-east-1", // default: 'us-east-1', optional
    });
    module.exports = Logger;

    Env Variables

      AWS_ACCESS_KEY_ID
      AWS_SECRET_ACCESS_KEY
  4. Slack Logger

    const PlayoLogger = require("@playo/logger");
    
    const Logger = new PlayoLogger("<service-name>");
    Logger.setSlack("<channel>");
    
    // <channel> is optional, default is 'general'
    
    module.exports = Logger;

    Env Variables

      SLACK_TOKEN
  5. Custom keys

    const PlayoLogger = require("@playo/logger");
    
    const Logger = new PlayoLogger("<service-name>");
    Logger.set(key, value);
    
    module.exports = Logger;

    set can be used in the file which requires the logger instance

Example with mail and slack Logger

const PlayoLogger = require("@playo/logger");

const Logger = new PlayoLogger("utils");

Logger.setSlack("server_alerts");
Logger.setMailer({
  receiverEmail: ["[email protected]"], // array of recievers, mandatory
  senderEmail: "[email protected]" // address of sender, mandatory
});
module.exports = Logger;

Pass Env for mail and slack logger

  AWS_ACCESS_KEY_ID
  AWS_SECRET_ACCESS_KEY
  SLACK_TOKEN

How to Log

Logger.debug(id, data, message);
Logger.info(id, data, message);
Logger.error(id, data, message);

On Critical Logs, Put both error and alert log

Logger.alert(id, data, message);
Logger.error(id, data, message);