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

express-wiretap

v1.1.2

Published

server wire logs and insights for express

Downloads

30

Readme

express-wiretap

server wire logs and insights for express

This express middleware provides a wire log for any express server, which is very useful for debugging, or in servers where minute audit is needed

Usage

Better see an example:

const express = require ('express');
const wiretap = require ('../');


const cfg = {
  logger: {
    verbose: function () {console.log.apply (console, arguments)},
    info:    function () {console.log.apply (console, arguments)}
  }
};

const app = express ();
const wt = new wiretap (cfg);
app.use (wt.mw ());

app.all ('*', (req, res) => {
  req.on ('end', () => {
    res.send ({q: req.query, hdr: req.headers});
  });
});

app.listen (6677, () => {
  console.log ('ready');
});

The middleware is created using a opts object:

  • logger: the logger to use. It expects a simple object with 2 methods, verbose and info, where each take the same arguments a console.log call would: a string and extra params to substitute in the util.format fashion. You can see a simple logger in the example above

with the server above running, you can call it:

$ curl -X POST --data-bin 'qwertyuiopqwertyuiopqwertyuiopqwertyuiopqwertyuiopqwertyuiop' http://localhost:6677/a/b/c?ggg=yyyyyy

and you'd get the following log:

- - wiretap < POST /a/b/c?ggg=yyyyyy HTTP/1.1
- - wiretap < Host: localhost:6677
- - wiretap < User-Agent: curl/7.64.0
- - wiretap < Accept: */*
- - wiretap < Content-Length: 60
- - wiretap < Content-Type: application/x-www-form-urlencoded
- - wiretap <
- - wiretap < qwertyuiopqwertyuiopqwertyuiopqwertyuiopqwertyuiopqwertyuiop
- - wiretap > HTTP/1.1 200 OK
- - wiretap > X-Powered-By: Express
- - wiretap > Content-Type: application/json; charset=utf-8
- - wiretap > Content-Length: 169
- - wiretap > ETag: W/"a9-FyQ6MRGi44gyIl3jwXCNLLwq6ng"
- - wiretap > Date: Wed, 16 Oct 2019 15:13:54 GMT
- - wiretap > Connection: keep-alive
- - wiretap >
- - wiretap >
- - wiretap > {"q":{"ggg":"yyyyyy"},"hdr":{"host":"localhost:6677","user-agent":"curl/7.64.0","accept":"*/*","content-length":"60","content-type":"application/x-www-form-urlencoded"}}

Notes

  • The wire log is not pitch-perfect: it is not a full log attached to the socket. For example, any 100-continue exchange is not shown
  • If the reqs are marked with an id (such as when using express-request-id) the id is included in the log