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

@har-tools/stream

v0.1.2

Published

Create a stream of HAR entries from the Fetch API Request/Response instances

Downloads

10

Readme

@har-tools/stream

Create a stream of HAR entries from the Fetch API Request/Response instances.

Installation

npm install @har-tools/stream

Usage

import { HarStream, NetworkEntry } from '@har-tools/stream'

// Create an HAR stream.
const stream = new HarStream()

// Create a new network entry.
const entry = new NetworkEntry(new Request('https://example.com'))

// Write the network entry early.
// As soon as you ".end()" the entry with a Response,
// the stream will emit the complete HAR entry.
stream.write(entry)

// Call the ".end()" method once you receive the response.
entry.end(new Response('Hello world'))

Listening to HAR entries:

stream.on('data', (entry) => {
  // Observe generated HAR entries as they come in.
  console.log(entry.request, entry.response)
})

Stop the stream:

stream.destroy()

Timings

You can control the network entry timings using the entry.timings API. It provides you with the methods you have to call sequentially to indicate various staged of the request.

The order of the timing metrics:

  1. socketOpened, socket opened but not connected yet.
  2. dnsLookupEnd, socket has resolved the DNS name.
  3. connected, socket has connected.
  4. connectedSecure (Optional)
  5. requestEnd, request is finished (request headers and body sent).
  6. responseStart, first byte of the response received.
  7. responseEnd, last byte of the response received.

Entry timings are dependent, so if the previous timing is missing, the next one will not be calculated. For example, if entry.timings.dnsLookupEnd() was never called, the network entry will have both dns and connected timings as -1.