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

xlog

v0.0.1

Published

Extends console.log and console.err to add a prefix which contains the node.js PID and the http request URL and an identification counter.

Downloads

5

Readme

xlog

Simple express/connect middleware that extends console.log and console.err to add a prefix which contains the node.js PID and the http request URL and an identification counter.

The node implementation at Yahoo uses cluster that spawns multiple processes that handle internet traffic. There are some situation when errors are logged but it is not clear what caused it, this is specially true of uncaught exceptions. This module captures the most common async functions available in node so it can capture the request and display the information in the error log.

Both the console.log and console.error are extended to display the PID of the process that generated the log as well as the request method and URL path. This information is only displayed the first time a log is generated for a request when it is indexed. Subsequent logs will only show the PID and the index.

For example is there are two entry points ('/getUser' and '/setUser') with GET and POST methods the log file could look something like:

[1234:1] Method: GET - url: /getUser 
[1234:1] GetMessage1`
[1234:2] Method: POST - url: /setUser
[1234:2] PostMessage1
[1234:1] GetMessage2
[1333:3] Method: GET - url: /getUser
[1333:3] GetMessage2User</br>
[1333:3] GetMessage2</br>

The exception to the indexing rule is uncaught exceptions when the module will always display the PID and request information.

install

With npm do:

npm install xlog

usage

var express = require('express'),
    xlog = require('xlog');

var app = express();

app.use(xlog());

app.listen(8000);