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

console_extension

v1.0.1

Published

A lib to change default default of the console object, in order to do extended logs.

Downloads

5

Readme

Adding some features over console methods to log objects.

To log INFO|WARN|DEBUG|ERROR objects use:

Logging some message:

Use common log methods to log different levels of information.

console.info( 'Foo' );
//or
console.info( { message: 'Foo' } );

Output will be this a stringified object like this:

{
  "message": "Foo",
  "system": "Your system name",
  "service": "your service name",
  "hostname": "Machine name",
  "type": "log",
  "level": "INFO",
  "timestamp": "2017-09-01T02:34:53.134Z"
}

Using different log levels

The level prop varies according to the method called:

console.info(); // level: INFO
console.warn(); // level: WARN
console.debug(); // level: DEBUG
console.error(); // level: ERROR

Logging properties:

You can add any props to the output object, simple logging a object with those

console.info( { message: 'Foo', custom_field: 'customize', another_field: 'more_values' } );

Outputs:

{
  "message": "Foo",
  "custom_field": "customize",
  "another_field": "more_values",
  "system": "Your system name",
  "service": "your service name",
  "hostname": "Machine name",
  "type": "log",
  "level": "INFO",
  "timestamp": "2017-09-01T02:34:53.134Z"
}

Note that you cannot overwrite the default props

To log metrics

Use V8 native method table to log a metric object.

console.table( { custom_field: 'bar', another_field: 'bar' } );

Is almost the same object:

{
  "custom_field": "bar",
  "another_field": "bar",
  "system": "Your system name",
  "service": "your service name",
  "hostname": "Machine name",
  "type": "metric",
  "timestamp": "2017-09-01T02:34:53.134Z"
}

Note that you do not have a level anymore, nor a message

Automatic fields:

These are the fields added by default by the lib (an their values):

  • system: Read from process.env.SYSTEM_NAME
  • service: Read from process.env.SERVICE_NAME
  • hostname: Read from require('os').hostname()
  • type: Automatic set for 'log' or 'metric'
  • level: Log only. Set after the method called
  • timestamp: Current date in ISO-8601 format