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

@clearonline/express-request-capture

v0.0.3

Published

Node.js express middleware for capturing HTTP request and responses

Downloads

6

Readme

express-request-capture

Node.js express middleware for capturing HTTP requests and responses

NPM Version NPM Downloads

Install

npm install @clearonline/express-request-capture

API

var requestCapture = require ('@clearonline/express-request-capture')

requestCapture ({ channel: string, url?: string })

When using this module with express or connect, simply app.use the module. Request information url, request, response, status, latency, and clientIp, is printed/stored to the specified channel!

var requestCapture = require ('express-request-capture'),
    express = require ('express')

var app = express()

var printAdapter = { channel: 'console|http|mongo|mysql', url: 'required if channel is either http or database' };
app.use(requestCapture(printAdapter))
// sample response
{
    url: "https://alert.clearonline.org/api/v1/subscribe",
    method: "POST",
    status: 200,
    latency: 100,
    request: {
        headers: {
            "Content-Type": "application/json"
        },
        body: {
            email: "[email protected]",
            trigger: "solar energy"
        },
        host: "localhost:3000",
        clientIp: "192.111.1.1"
    },
    response: {
        header: {
            "Date": "2017-06-02T22:29:44.315Z"
        },
        body: {
            message: "Thank you for subscribing, i will send you notes every monday!"
        }
    }
}

Examples

License

MIT

Chanelog

[06-02-2017] only console is supported

Blog

Description

Monitoring your web app is one the many ways to prevent hackers from breaking your app. In this tutorial, we do this by creating an expressjs middleware that logs all information related to the received request and return response.

Goal

Capture all requests (request and response) that my express application handles.

Step by Step

  • initialize npm package
mkdir express-request-capture && cd express-request-capture
npm init -y
  • create index.js file
# this will be the entry/main file of our middleware
touch index.js
  • add content to index.js file
module.exports = require('./src/capture.js')
  • create the src folder
mkdir src
  • create a capture.js file inside src

  • put logic inside the capture.js file

  • publish to npm

npm login
npm publish
    1. use the middleware