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

heroku-log

v1.4.0

Published

console.log wrapper for heroku-like logs

Downloads

8

Readme

Heroku-log

Console.log wrapper for heroku-like logs

Build Status

Install

yarn

yarn add heroku-log

npm

npm install heroku-log --save

Available levels

import {
  info,
  debug,
  error,
  warn,
  trace,
  fatal
} from 'heroku-log'

Example

import herokuLog, { error } from 'heroku-log'

// # On Heroku
herokuLog.info('Server is starting')
// 2017-05-24T08:58:42.857401+00:00 app[web.1] level=info message="Server is starting"

error(new Error('I am an error '))
// 2017-05-24T08:58:42.857401+00:00 app[web.1] level=error error="I am an error"

Tricks

Sometimes you don't want those logs e.g. when testing things, in this case you can pass a env variable in the command line and the module is muted

$ HEROKU_LOG=disable mocha test.js

Timestamps

If the environment is not production heroku-log will add a simple time-mark at the beginning of each log, in production it will be hidden since Heroku adds a time block by itself.