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

@homeappcorporate/logger

v1.0.0

Published

####Introduction

Downloads

3

Readme

Logger · npm version

####Introduction

Zero dependencies Logger module, for consoling messages with given level and metadata.

Installing

$ yarn add @homeappcorporate/logger

or

$ npm install @homeappcorporate/logger --save

Usage

For initialization, you need to create an instance of the Logger.

Basic example:

import Logger from '@homeapp/logger';

const logger = new Logger();

logger.error(new Error('Some message'), { someMeta: 'someValue' });
logger.info('Info message', { someMeta: 'someValue' });

Logger constructor Parameters

| Parameter | Type | Default | Required | Description | | --------- | ---------------- | ------- | -------- | --------------------------------------------------------------------- | | loggers | array<object> | [] | no | List of loggers, must have required methods (error, info, warn) |

Logger instance Methods

| Method | Description | | ---------------------- | ------------------------------------------------------- | | error(event, metadata) | Consoling a given event with error level | | info(event, metadata) | Same as error(event, metadata), but with level info | | warn(event, metadata) | Same as error(event, metadata), but with level warn |

WARNING! Every logger, which was passed into loggers array in a constructor, must have three required methods: error, warn and info.

Usage example

import Logger from '@homeapp/logger';

function post(event, meta, level) {
  console.log(`...requesting custom logger to remote server with level - ${level}`);
  fetch('hhtp://some-logger-server', {
    method: 'POST',
    body: JSON.stringify({ event, meta, level }),
  });
}

class MyCustomLogger {
  constructor(config) {
    // some cutom logic
  }

  error(event, metadata) {
    post(event, metadata, 'error');
  }

  warn(event, metadata) {
    post(event, metadata, 'warn');
  }

  info(event, metadata) {
    post(event, metadata, 'info');
  }
}

const customLogger = new MyCustomLogger({ someConfig: 'value' });
const logger = new Logger({ loggers: [customLogger] });

logger.error('Some message', { someMeta: 'someValue' });

this code will console

 Error: Some message
 meta data: {
   "someMeta": someValue
 }
 ...requesting custom logger to remote server, with level error