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

bts-logging

v0.1.1

Published

Very simple logger factory based on log4js

Downloads

5

Readme

bts-logging

Very simple logger factory based on log4js

Install

npm install bts-logging

Overview

Small logger factory just to save me rewriting something similar for every project.

Supports a global log level set via environment variable (to override the default level of 'INFO') and per-logger log levels.

Configuration

Define a logging.js file in your application project as follows:

module.exports = require('bts-logging')(__dirname, {
    logCfgFile: '../config/logging.json',
    logFilesDir: '../logs'
});

Adjust paths to configuration file and log directory as appropriate obviously.

A sample logging.json file is provided in this project. Copy to your own application and adjust as necessary. Log4js documenation is here.

Usage

var logging = require('./logging');                            // Path to your logging.js file as described above

var logger = logging.createLogger('foo');                      // Use default log level of 'INFO'
var logger = logging.createLogger('bar', 'DEBUG');             // Use custom log level
var logger = logging.createLoggerFromFileName(__filename);     // If __filename is 'foo.js', creates a logger with name 'foo' 

// Use log4js logger returned. See log4js docs linked above for details
logger.trace('blah');
logger.info('etc');

Run your app with LOG_LEVEL=X, where X = 'TRACE' | 'DEBUG' | 'INFO' | 'WARN' | 'ERROR', to override the default log level of 'INFO'

License

MIT