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

loggers-factory

v1.1.3

Published

Javascript package that makes the use of loggers a breath.

Downloads

21

Readme

Loggers Factory

NPM version Github issues NPM downloads Github stars

Javascript package that makes the use of loggers a breath. It relies on the winston module. There's a lot of room for improvement but it does the job nonetheless. Enjoy :) !!

Setup

Install the loggers factory in your project as an NPM dependency :

npm install loggers-factory

You can also clone it into your project directory from loggers-factory GitHub repository:

git clone https://github.com/pasdechancee/loggers-factory.git

Usage

Default logger

const get_logger = require("loggers-factory");

const logger = get_logger();
// => your default logger !

logger.info("Hello world !");

Console output:

2018-12-09T13:17:34.768Z [MAIN.7532] info: Hello world !

Log output:

{"timestamp":"2018-12-09T13:17:34.768Z","level":"info","source":"MAIN.7532","message":"Hello world !"}

Custom logger

You only have to change the values that you'd like to custom ! Your custom parameters will be deep merged with the default ones.

const get_logger = require("loggers-factory");

const custom_params = {
	source: "my_app", // this changes the logs label.
	// This is your new default logs folder path.
	logs_path: "my_app/folder/logs",
	level_design: {
		levels: {
			// min level = 5... This is a point to improve !
			// we're not able to insert levels in betwee nthe existing ones.
			verbose: 5
		},
		colors: {
			// custom style if you don't like the winston default.
			verbose: "italic bold grey"
		}
	},
	transport: {
		console: {
			// The console is disabled in PRODUCTION env.
			level: "warn"
		},
		logs: {
			combined: {
				// This overwrites the default logs folder path.
				logs_path: "my_app/folder/logs/combined"
			},
			errors: {
				// customed_winston_format = winston format that you created.
				format: custom_winston_format
			},
			custom_log: {
				name: "custom",
				level: process.env.LOG_CUSTOM_LEVEL || "debug",
				logs_path: "my_app/folder/logs",
				format: custom_winston_format,
				date_pattern: "DD-MM-YYYY",
				// see https://github.com/winstonjs/winston-daily-rotate-file
				// for max_size and max_files format.
				max_size: undefined,
				max_files: "14d",
				on_limit: undefined // rotation not supported yet !!
			}
		}
	}
};

const logger = get_logger(custom_params);
// => your customed logger !

.env variables

You can set up your own .env variables if you want. If you don't, the module will set these by default.

If you have your own .env variables, you don't have to set them in your custom parameters anymore.

LOG_PATH = "my_app/folder/logs";
LOG_CONSOLE_LEVEL=info
LOG_COMBINED_LEVEL=debug
LOG_ERRORS_LEVEL=error
LOG_"any custom level you want"_LEVEL=silly

Contributing

Please read the CONTRIBUTING document before making changes that you would like adopted in the code.


© MIT license Contact: [email protected]