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

@adazes/log4js

v1.0.7

Published

a simple, very light-weight Logger implementation for JS (inspired by log4j)

Downloads

20

Readme

log4js

A simple, very light-weight Logger implementation for JS (inspired by log4j)

Installation

npm i --save-dev @adazes/log4js

Usage

Importing

Node.js

import * as log4js from "@adazes/log4js";

Browsers

<script src="your/js/include/path/log4js-for-browsers.min.js" type="text/javascript"></script> <!-- 6.6KB -->

Using (both (Node.js & Browsers))

var logger = new log4js.Logger("Demo", 
	log4js.Level.WARN,  // Level.OFF can also be used to turn logging off completely
	true);
if (logger.isInfoEnabled())
	logger.info("This isn't logged since level is higher than threshold set");

var logger2 = new log4js.Logger({
	name: "Logger initialized with a config object",
	level: log4js.Level.ALL,
	useLevelAbbreviation: true});
logger2.all("This is logged");
// A> Logger initialized with a config object (2022-6-10, 14:14:30): This is logged

Config object usable during construction (with default values indicated)

{
	name: '',
	level: log4js.Level.INFO,
	skipPrefix: false,
	skipTimestamp: false,
	skipName: false,
	useLevelAbbreviation: false,
	dateFormatter: new Intl.DateTimeFormat(navigator.language+ "-u-ca-iso8601", {
		  year: 'numeric', month: 'numeric', day: 'numeric',
		  hour: 'numeric', minute: 'numeric', second: 'numeric',
		  hour12: false
	}
}

These same settings can be passed in, in this exact order, as individual constructor parameters, which frequently results in less typing. See var logger for an example in Using section above.

Demo

Feel free to take a look at the demo for live examples of logging code & messages logged in browser console.

Automated testing

git clone https://github.com/haqer1/log4js.git
cd log4js
npm install
npm run test