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

unibot-logmodule

v1.0.3

Published

A small npm module to deal with logs in a node application

Downloads

5

Readme

LogModule

Introduction

This module's purpose is to handle the logs in a node application. It contains one class LogModule which contains a logger to log in console and in a file if desired and send it to the remote LogService so other clients can access these logs.

LogModule class

Fields

  • logger : this field contains the logger (winston logger)
  • logUrl: this field contains the Log Service URL (set in constructor)
  • serviceName: the name of the service that wants to log (set in constructor)
  • accessToken: the access token used to authenticate (set in constructor)

Constructor

public constructor(accessToken: string, logUrl: string, serviceName: string, pathLog = ''); If pathLog != '', the module will log in console and in the file pointed by the path pathLog

Methods

  • public async log(detail: string, level:string, date:Date, remote=true): log the message detail with level level at the moment date, if remote is true, then the log will be sent to the log service
  • public async warn(detail: string, date:Date, remote=true): log with level warn
  • public async info(detail: string, date:Date, remote=true): log with level info
  • public async error(detail: string, date:Date, remote=true): log with level error

Exemples

  • Instantiate the LogModule
    const access_token = 'd75200fa-5080-4c34-81d6-1f68400f9b89';

const log = new LogModule(access_token, 'http://localhost:8080', 'TestLog');

  • Log only in console
    log.log('Une information', 'INFO', new Date(Date.now()), false).catch((error) => console.log(error)); log.warn('Un avertissement', new Date(Date.now()), false).catch((error) => console.log(error));

log.error('Une erreur', new Date(Date.now()), false).catch((error) => console.log(error));

  • Log with save file
    const log2 = new LogModule(access_token, 'http://localhost:8080', 'TestLog', '../../sys2.log');

log2.log('Une information', 'INFO', new Date(Date.now()), false).catch((error) => console.log(error));

log2.warn('Un avertissement', new Date(Date.now()), false).catch((error) => console.log(error));

log2.error('Une erreur', new Date(Date.now()), false).catch((error) => console.log(error));

  • Log with remote without save file
    const log3 = new LogModule(access_token, 'http://localhost:8080', 'TestLog');

log3.log('Une information', 'INFO', new Date(Date.now())).catch((error) => console.log(error));

log3.warn('Un avertissement', new Date(Date.now())).catch((error) => console.log(error));

log3.error('Une erreur', new Date(Date.now())).catch((error) => console.log(error));

  • Log with remote with save file
    const log4 = new LogModule(access_token, 'http://localhost:8080', 'TestLog', '../../sys3.log');

log4.log('Une information', 'INFO', new Date(Date.now())).catch((error) => console.log(error));

log4.warn('Un avertissement', new Date(Date.now())).catch((error) => console.log(error));

log4.error('Une erreur', new Date(Date.now())).catch((error) => console.log(error));

  • Test with bad file directory
    const log5 = new LogModule(access_token, 'http://localhost:8080', 'TestLog', '../..');

log5.log('Une info', 'INFO', new Date(Date.now()), false).catch((error) => console.log(error));