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

@ocelotjungle/logger

v1.0.2

Published

Configurable logger with subloggers and file support

Downloads

3

Readme

@ocelotjungle/logger

This package provides a Logger class with configurable outputs and levels, and ability to create subloggers.


Usage

Constructor

It takes either nothing or just logger name or an options object:

  • name is a name of a logger;
  • options:
    • dateFormatter is a function that stringifies Date, can be one of presets or custom;
    • levels can be:
      • max level that is written to logs (for example, error, then warnings, info etc won't be printed);
      • object with explicitly defined levels;
    • unite - if true, then all outputs are accumulated till you use end();
    • defaultLogOptions is a log options that are applied to every log by default;

Methods

withConsole

Adds console to logger outputs. Can be default (global.console) or custom.

withFiles

Adds files to logger outputs:

  • folder is an absolute path or relative to project root path where logs will be written;
  • name is a left log files name (*name*(.suffix)?.extension);
  • extension is a log files extension (name(.suffix)?.*extension*);
  • levels is similar to constructor's options levels, except common level, which is general file for all logs;

Logging functions

  • error - level 1, errors;
  • warn - level 2, warnings;
  • info - level 3, info messages;
  • dev - level 4, info messages for development/debugging;
  • end - frees accumulated messages if unite, else does nothing;

Utils

  • sub - creates sublogger, copying the master logger parameters;
  • bound - returns a scope of logger functions, bound to the logger;

Examples

const logger = new Logger("master logger").withConsole()
logger.info("sample info message") // [iso-datetime] (master logger) ||| sample info message

const sublogger = logger.sub("sublogger", unite = true)
const { dev, env } = sublogger
dev("dev message 1") // prints nothing
dev("dev message 2") // prints nothing
end() // prints both previous messages in one operation, not broken my any other logger intermediate output

const subsublogger = sublogger.sub("subsublogger", unite = false, { depth: null })
subsublogger.error({ foo: { bar: { ... } } }) // prints argument inspected with no depth constraint, as console.dir(..., { depth: null }) would