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

socket-recorder

v1.1.0

Published

Record and log all socket transactions that occur for a specific period of time

Downloads

5

Readme

socket-recorder

Record and log all communication over sockets.

Build Status

Patching Socket

When using SocketRecorder, net.Socket needs to be patched before anything else extends or creates a Socket in order for that to be recorded. Patching can be done by either calling patch() or by assigning record:

require('socket-recorder').patch();

// automatically patches when retrieving the record method:
const { record } = require('socket-recorder');

// net Socket can also be unpatched:
require('socket-recorder').unpatch();

Basic usage

const { record } = require('socket-recorder');

// basic recording of process.stdout
record((done) => {
  console.log('Hello, world!');
  console.log('Goodbye, world!');
  done();
}, (log) => {
  // returns an array of sockets and their messages
});

// or use it as a Promise
record((resolve, reject) => {
  console.log('I promise!');
  resolve();
}).then((log) => {

});

Response from console.log:

[
  {
    events: [
      { request: 'Hello, world!\n', created_at: 1489460314753.3242 },
      { request: 'Goodbye, world!\n', created_at: 1489460314753.4758 }
    ],
    source: 'stdout'
  }
]

More advanced responses

const { record } = require('socket-recorder');
const express = require('express');

// recording of an HTTP transaction
const app = express();
app.get('/', (req, res) => {
  res.header('Content-length', 13);
  res.write('Hello, world!');
  res.end();
});
const server = app.listen(8888, () => {
  record((done) => {
    http.get('http://localhost:8888', done);
  }, (log) => {
    // returns an array of sockets and their messages,
    // both request and response
    server.close();
  });
});

Response from HTTP transaction:

[
  {
    events: [
      {
        request: 'GET / HTTP/1.1\r\nHost: localhost:8888\r\nConnection: close\r\n\r\n',
        created_at: 1489460545620.1575
      },
      {
        response: 'HTTP/1.1 200 OK\r\nX-Powered-By: Express\r\nContent-length: 13\r\nDate: Tue, 14 Mar 2017 03:02:25 GMT\r\nConnection: close\r\n\r\nHello, world!',
        created_at: 1489460545628.0654
      }
    ],
    connection: {
      host: 'localhost',
      port: '8888'
    },
    source: 'tcp'
  }
]