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

lw-logger

v1.1.0

Published

Relays log entries to the LW Logging Service. Can also be used to log Express requests.

Downloads

10

Readme

Lone Wolf Logger

The Lone Wolf Logger relays log messages to the Lone Wolf logging service. Can also be used to log Express requests.

Tests are run using Mocha. You must install mocha globally as it's not part of this repoository. To run all tests, use the following command from the root repository folder: mocha.

Contribution guidelines

  • Before any commits are done, unit tests must be written to cover any new code or challenges fixed. There should be 100% code coverage after every commit.
  • To do a code coverage run, use the following command from the root repository folder: istanbul cover _mocha -- -R spec

Sample Config

{
    "options": {
        "debug": false,
        "console": true,
        "level": "info",
        "name": "default"
    },
    "service": {
        "name": "a-service",
        "hostname": "localhost"
    },
    "relay": {
        "host": "logging-service",
        "port": 1234,
        "uri": ""
    }
}

options

Contains config for the logger itself.

options.debug (defaults to false)

If 'true', the logger itself will display any debug entries.

options.console (defaults to true)

If 'true', the log entries will be sent to the console.

options.level (defaults to trace)

The minimum level of log severity that the logger should log. Anything below this setting will be ignored.

Log Levels

  • trace
  • info
  • warn
  • error
  • fatal

options.name (defaults to LWLogger)

The name of the logger. This will only appear in console logs.

service

Contains config for the service that is doing the logging. Various information in this config will be relayed to the logging service.

service.name

Added to the meta data as 'serviceName' when a log entry is relayed to the logging service.

service.hostname

Added to the meta data as 'hostId' when a log entry is relayed to the logging service.

relay (optional)

Contains config about the service that the logs should be relayed to. If the relay config is not provided relay will be disabled.

relay.host

The hostname of the relay service (IE: clio). Required if relay config is provided. If not provided relay will be disabled.

relay.port (optional)

The port of the relay service. If not provided, the default of 80 will be used.

relay.uri (optional)

The URI that logs should be relayed to on the service. (IE: A setting of 'logs' will result in a relay URL of: http://clio:80/logs)

Usage

var LWLogger = require('lw-logger');

var logger = LWLogger.configure(config);

logger.info('Hello!');

Usage With Express

var LWLogger = require('lw-logger');

LWLogger.configure(config);

var app = express();

app.use(LWLogger.requestLogger());