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

@vrscheduler/logger

v1.2.1

Published

Handles logging on local and production environments

Downloads

5

Readme

@vrscheduler/logger

Logging microservice that includes the ability to print to console and/or to a log file.

Installations

npm install @vrscheduler/logger

Usage

The logger uses a singleton approach whereby the first time you call the call you must use the following code:

import { Logger } from "@vrscheduler/logger"; const logger = Logger.createInstance({ timestamp: true }, 'console');

The createInstance method is shown below:

static createInstance(options: LoggerOptions, ...types: loggers[]): Logger;

where loggers accepts the following options:

  • console
  • file
  • fluent

Logger options is described below:

type LoggerOptions = {
  timestamps: boolean
  fluent?: FluentOptions
  file?: FileOptions
}

export type FluentOptions = {
  host?: string
  port?: number
  timeout?: number
}

export type FileOptions = {
  dirName: string
}

For Fluent it is also possible to pass through host, port and timeout parameters through environment variables FLUENT_HOST, FLUENT_PORT and FLUENT_TIMEOUT. The default port for fluent is 24224 and default timeout is 3000

When using the logger in other files you can use the following line to get the logger instance instead of creating it again:

const logger = Logger.getInstance()

When using the file logger, it will create files in the directory name provided in the createInstance() method.

Three files are used. log(), debug(), error() and metric() will go into general.log, debug.log, error.log and metric.log file respectively.

Future features