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 🙏

© 2026 – Pkg Stats / Ryan Hefner

networkdiagnosistool

v1.0.4

Published

A Node.js tool for network diagnosis using MTR and DNS resolution.

Readme

Network Diagnosis Tool

中文說明 (Traditional Chinese)

A Node.js package for diagnosing network connection quality. It supports retrieving local network information, DNS resolution, and performing MTR (My Traceroute) tests.

Features

  1. Local Network Info: Automatically retrieves local IPv4, IPv6 addresses, and system DNS servers.
  2. DNS Resolution: Resolves target domains to obtain target IP addresses.
  3. MTR Testing: Performs MTR-like analysis using system ping to analyze connection status for each hop.
  4. Dual Mode Support: Supports both Promise Chain (Async/Await) and Stepwise Callback execution patterns.
  5. Report Generation: Generates a complete JSON diagnosis report.

Requirements

This package relies on the system's ping command, which is typically pre-installed on most operating systems.

  • Windows: ping is built-in.
  • Linux: iputils-ping or similar (usually pre-installed).
  • macOS: ping is built-in.

Install package dependencies:

npm install

Usage Examples

1. Promise (Async/Await) Version

Suitable for simple scripts or scenarios where only the final report is needed.

const Diagnosis = require('./index');

const domains = ['google.com', 'github.com'];
const duration = 5; // MTR test duration (cycles)

const tool = new Diagnosis(domains, duration);

async function main() {
    try {
        console.log('Diagnosis starting...');
        const report = await tool.run();
        console.log('Diagnosis completed!');
        console.log(JSON.stringify(report, null, 2));
    } catch (err) {
        console.error('Error during diagnosis:', err);
    }
}

main();

2. Callback Version (Stepwise Progress)

Suitable for scenarios like frontend UIs where real-time progress updates (e.g., "Resolving DNS", "Running MTR") are needed.

const Diagnosis = require('./index');

const domains = ['google.com'];
const duration = 3;

const tool = new Diagnosis(domains, duration);

tool.run((progress) => {
    const { step, status, domain, data, error } = progress;
    
    switch (status) {
        case 'starting':
            console.log(`[Start] Step: ${step} ${domain ? `for ${domain}` : ''}`);
            break;
        case 'completed':
            console.log(`[Done] Step: ${step} successful.`);
            if (step === 'finished') {
                console.log('Final report generated.');
            }
            break;
        case 'failed':
            console.error(`[Error] Step: ${step} failed: ${error}`);
            break;
        default:
            // Handle other statuses like 'resolving', 'running', etc.
            break;
    }
}).then((finalReport) => {
    // Even with Callback, run() still returns a Promise resolving to the final report
    console.log('All tasks finished.');
});

Report Structure (JSON)

{
  "timestamp": "ISO-8601 Timestamp",
  "localNetwork": {
    "ipv4": ["192.168.1.100"],
    "ipv6": ["fe80::..."],
    "dnsServers": ["1.1.1.1"]
  },
  "diagnosis": [
    {
      "domain": "google.com",
      "dns": {
        "resolved": true,
        "addresses": ["142.250.204.46"],
        "error": null
      },
      "mtr": {
        "executed": true,
        "hops": [
          { 
            "host": "192.168.1.1", 
            "ip": "192.168.1.1", 
            "loss": 0, 
            "avg": 1.5, 
            "best": 1.2, 
            "worst": 2.1, 
            "stdev": 0.3 
          }
        ],
        "error": null
      }
    }
  ]
}