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

logstar

v3.1.0

Published

Simple, opinionated, isomorphic logging.

Downloads

39

Readme

logstar

Travis Status devDependency Status Dependency Status

Simple, opinionated, isomorphic logging.

It uses winston on the server and console.log on the client. It supports multiple arguments. If you have LOGGLY environment variables set, it will auto-configure the winston loggly transport.

Usage

import * as Logstar from 'logstar';

Logstar.debug('foo');
Logstar.info('bar');
Logstar.fatal('error', new Error('error'));

API

class Logger

import { Logger } from 'logstar';

constructor(options = {})

Configure loggly here. Optionally provide a globalMeta object to be attached to each log request.

{
  logLevel: 'info',
  loggly: {
    token: '',
    subdomain: '',
    tags: '',
  },
  globalMeta: {}
}

For JSON-logging, the following rules apply:

  1. If there are exactly 2 arguments passed to the log function, and the second argument is an object, then that object is used as the meta parameter, and the first argument is used as the log message.
  2. If there is exactly 1 argument passed to the log function, and that argument is an object, then that object is used as the meta parameter, with an empty log message.
  3. In all other cases, the first argument is used as the log message, and the subsequent arguments are added as the context property on the meta object.

debug(...args)

debugf(format, ...args)

info(...args)

infof(format, ...args)

warn(...args)

warnf(format, ...args)

error(...args)

errorf(format, ...args)

fatal(...args)

fatalf(format, ...args)

transactionLogger

Get a logger that adds a transaction_id property to the meta. Useful for tracking related requests.

import { transactionLogger } from 'logstar';
const myLogger = transactionLogger('TRANSACTION-ID');

default

Logger pre-configured with loggly parameters from environment variables. (See below)

import Logstar from 'logstar';

Logstar.info('Hello', 12, { foo: 'bar' }, [1, 2, 3], new Error('Hello'));

// This will end up as:
{"level": "info", "message": "Hello", "context": [12, {"foo": "bar"}, [1, 2, 3], "Hello"]}

Configuration

ENV VARIABLES

LOG_LEVEL="debug" # Defaults to info
LOGGLY_SUBDOMAIN="mysubdomain"
LOGGLY_TAGS="api-server,production"
LOGGLY_TOKEN="secret-loggly-token-here"