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

level-http-recorder

v7.2.1

Published

A rudimentary middleware / handler that records http requests to a local level db

Downloads

49

Readme

level-http-recorder Build Status stable

A rudimentary middleware / handler that records http requests to a local level db.

Compatible with various web frameworks that use standard middleware interface function (req, res, next) {}

This module expects the given db to support:

  • levelup interface
  • bytewise key encoding
  • json value encoding

normal use:

var stack = require('stack')
var db = require('level-bytewise')('./mydb')
var http = require('http')

var levelHttpRecorder = require('level-http-recorder')(db)

http.createServer(stack(levelHttpRecorder))

modify before a request is persisted

var stack = require('stack')
var db = require('level-bytewise')('./mydb')
var http = require('http')

var levelHttpRecorder = require('level-http-recorder')(db, function (requestData, request) {
    // do stuff to request data
    // DO NOT modify request!
    requestData.myField = 'foo'
})

http.createServer(stack(levelHttpRecorder))

schema

Every recorded request will have the following fields, represented here as the field name: the field name used to populate the value from the request object

    var result = {
        ip: request.ip, // if request had an ip property, this will be it
        requestId: [12312312312233,2] // the leveldb key of the request,
        method: request.method,
        httpVersion: request.httpVersion,
        headers: request.headers,
        url: request.url,
        trailers: request.trailers,
        time: Date.utc(),
        query: {}, // a parsed query string
        body: ... // if there is a body to the request and config.writeBody === true || request.writeBody === true - this field will hold the entire body. It is advisable to employ limit restrictions
    }