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

log-to-all

v0.1.4

Published

Combine a few loggers into one

Downloads

3

Readme

Log-To-All

NPM Version CircleCI Status

Installation

npm install log-to-all

or

yarn add log-to-all

Try it out to see how simple it is

Sample project for using the package

Basic example

This example use two of the implemented loggers:

const ConsoleLogger = require('log-to-all/lib/defaultLoggers/console');
const FileLogger = require('log-to-all/lib/defaultLoggers/file');
const logger = require('log-to-all').init([
  new ConsoleLogger(),
  new FileLogger(`${__dirname}/logs`)
]);
logger.info('♫♪♫♪!');

logger.debug('Will not be logged.');
logger.setDebugMode(true);
logger.debug('Now it will be logged.');

Implemented Loggers

Name| Description -------|------------------- console | Write the logs to the console file | Write the logs to files in the given path

 

const ConsoleLogger = require('log-to-all/lib/defaultLoggers/console');
const FileLogger = require('log-to-all/lib/defaultLoggers/file');

Add your own logger

In order to add your own logger all you have to do is to create new class with the functions:

  • debug(msg, params) - Will log only if debug mode set to true.
  • info(msg, params)
  • warn(msg, params)
  • error(msg, params)

It is recommended to use our base logger in order to make sure everything is implemented:

const baseLogger = require("log-to-all/lib/logger");
class YourLogger extends baseLogger {
}

Then add it to the array of init function like this:

const YourLogger = require('./YourLoggerPath');
require('log-to-all').init([
  new YourLogger()
]);