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

ah-net

v0.2.0

Published

Tracks async hook events related to network operations.

Downloads

14

Readme

ah-net build status

Tracks async hook events related to network operations.

Installation

npm install ah-net

API

NetworkActivityCollector

Instantiates a NetworkActivityCollector.

Most of the actual processing of resources is performed by th @see NetworkResourceProcessor.

Extends ActivityCollector and thus exposes the same public API with added functionality.

Parameters

  • $0.start Array<number> the start time of the process, i.e. the result of process.hrtime()
  • $0.stackCapturer StackCapturer? see ah-stack-capturer which configures how and when stacks traces are captured and processed.By default a StackCapturer is used that captures stacks for all events for file system related types: FSREQWRAP, FSREQUESTWRAP and some others like TickObjects that also are related, i.e. if they contain information related to streams. (optional, default StackCapturer)
  • $0.bufferLength number? determines how many elements of Buffers are captured. By default not Buffer data is captured. (optional, default 0)
  • $0.stringLength number? determines how much of each string is captured. By default no string data is captured. (optional, default 0)
  • $0.captureArguments boolean? if true arguments of callbacks are captured when they are processed. (optional, default false)
  • $0.captureSource boolean? if true the source code of callbacks is captured when they are processed. (optional, default false)

NetworkResourceProcessor

Extends ResourceProcessor

The Network processor grabs information off the network socket itself, the server if present.

In the case of an http request the HTTPPARSR resource is present. It has a lot of useful properties attached to it, including incoming and outgoing http messages.

Below is a condensed outline of the HTTPARSER properties that are most relevant:

{
   socket: {
     _httpMessage {
           _header
         , statusMessage
         , statusCode
         , _headerSent
         , finished
           ...
      }
    , _handle: { fd, reading, _parent }
    , server: { _connectionKey }
  }
 , incoming {
     httpVersion*
   , headers: { host, connection }
   , upgrade
   , url
   , method
   , statusCode
   , statusMessage
  }
}

License

MIT