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

@k26pl/logger

v1.2.1

Published

A simple, universal and configurable logger for js and ts

Downloads

4

Readme

Logger

A simple, universal and configurable logger for js and ts

Usage:

Basic example:

import createLogger from "@k26pl/logger";

let logger = createlogger("example");

logger.log("Hello world");

Scopes

Scopes can help you distinguish logs from certain files, functions etc.
Example scope cration:

let function_logger = logger.scope("my_function");
function_logger.log("hi");
// console output:
// [log] [current time] [example:my_function]: hi

Destinations

By default log messages will go only to console.
You can change this by configuring destinations:

import {
  setDefaultDestinations,
  consoleDestination,
  fileDestination,
} from "@k26pl/logger";

setDefaultDestinations([consoleDestination(), fileDestination("./my_program.log")]);

or for specific logger:

import { createLogger, consoleDestination, fileDestination } from "@k26pl/logger";

createLogger("test", [fileDestination("./test_output.log")]);

Custom destinations

It is possible to create custom destinations,
for example to forward logs to centralised place.
Example destination:

export function myDestination(my_arg: string): LogDestination {
  
  // the function that gets called with every log
  return (log) => {
    let { 
      // "verbose" | "info" | "log" | "warn" | "error"
      // severity of the log
      level, 
      // string
      // Scope of the log
      scope, 
      // Date 
      // `time_short` and `time_long` Helpers can be used to
      // convert it to human-readable time.
      timestamp, 
      // any[]
      // stringify_unknown helper can be used to
      // convert any type to text
      message 
    } = log;
    // ...
  };
}

Replace console

You can use replace_console() to replace info, log, warn and error
on global console object. This is useful when dependencies are using raw console, and you want to redirect their output somewhere.