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

@anissoft/echo

v1.3.0

Published

HTTP requests debugging tool

Downloads

2

Readme

@anissoft/echo

Easy-to-use network intercepting tool for nodeJS

UI Example

Installation

npm --registry=https://registry.npmjs.org i @anissoft/echo@latest # add --save-dev if you have no intends to include it into production build, or --no-save if you want to use just debugging interface

Usage

UI for requests analysis

Import startUI command from package and execute it in the very beginning of your program. It will start the static server and provide the exact link to the web interface in terminal.

require('@anissoft/echo').startUI({ port: 4900 });
// or just
require('@anissoft/echo').start();

The best way to do so - is to place the above code in a separate file (e.g. debug.js) and import it in your application's entry point (e.g. index.js).

You may skip passing a port attribute, but it is easier to use the same port between restarts, so you dont need to search new url in logs every time.

Custom onRequest listeners (experimental)

You can capture all requests (incoming and outgoing) and run your custom callbacks for the next events:

| Event name | Description | Event content | |--------------------------------------|-------------------------------|--------------------------------------------------------------------------------------------------------------------| | RequestEvent.incomingRequestStart | received incoming request | method, url, timeStart, requestHeaders, request | | RequestEvent.outgoingRequestStart | sent request | method, url, timeStart, requestHeaders, request | | RequestEvent.incomingRequestFinish | sent response for request | method, url, timeStart, requestHeaders, request, statusCode, statusMessage, timeEnd, responseHeaders, response | | RequestEvent.outgoingRequestFinish | received response for request | method, url, timeStart, requestHeaders, request, statusCode, statusMessage, timeEnd, responseHeaders, response |

const { subscribe, RequestEvent } = require('@anissoft/echo');

const unsubscribes = [
  subscribe(
    RequestEvent.incomingRequestStart, 
    event => console.log('incoming-start', event),
  ),
  subscribe(
    RequestEvent.incomingRequestFinish, 
    event => console.log('incoming-end', event),
  ),
  subscribe(
    RequestEvent.outgoingRequestStart, 
    event => console.log('outgoing-start', event),
  ),
  subscribe(
    RequestEvent.outgoingRequestFinish, 
    event => console.log('outgoing-end', event)
  ),
];

Make sure not to expose any sensetive data from events
eg. personal data, API-keys or authorizations headers