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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@alpler/logger

v1.2.4

Published

A simple way to create log files

Readme

@alpler/logger

Table of Contents

Install

This is a NodeJs Module, it can be installed through the npm registry.

To install use the following command in your root directory.

$ npm install @alpler/logger

Introduction

This is a simple logger for NodeJs. It will generate to log Files in which messages can be logged. errors.log Will only include messages with a level higher than WARN log.log Will include all messages above the before set Log Level

Simple example of how use it

JavaScript:

const logger = require("@alpler/logger");
logger.setLogLevel(logger.LogLevel.INFO);
logger.log(logger.LogLevel.ERROR, "example.js:5", "There is no code left to execute :(");

TypeScript:

import * as logger from "@alpler/logger"

logger.setLogLevel(logger.LogLevel.INFO)
logger.log(logger.LogLevel.ERROR, "example.ts:3", "There is no code left to execute :( ") 

OUTPUT:

[21.02.2022] [01:08] ERROR example.ts:3 There is no code left to execute :(

Log Levels

Each Log Level describes the different importance of a message.

Types:

In the version 1.2.1 there are six different Log levels these are

Name | Value | Description ---------|----------|--------- FATAL | 5000 | Servere errors that might cause a crash ERROR | 4000 | Erros which may prevent normal execution of the program WARN | 3000 | Potential problems which could also just be nothing INFO | 2000 | Information about the progress of the program DEBUG | 1000 | Detailed tracing messages for the progress of the program ALL | 0 | All that could you ever want to log

Usages:

Setting the Log Level

Typescript:

logger.setLogLevel(logger.LogLevel.INFO)

JavaScript:

logger.setLogLevel(logger.LogLevel.INFO)

This will set the Level at which the logger will start writing it into the log.log and also the console

Logging a message

Typescript:

logger.log(logger.LogLevel.ERROR, "example.ts:3", "There is no code left to execute :(")

JavaScript:

logger.log(logger.LogLevel.ERROR, "example.js:5", "There is no code left to execute :(")

In this Case we pass a Log Level with a message so the logger can check if the message should be logged.