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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@frozenjs/express-status-monitor

v2025.6.22

Published

Realtime monitor for Express server appliations

Readme

@frozenjs/express-status-monitor

express-status-monitor on npm npm TypeScript

A modern, TypeScript-ready, self-hosted monitoring solution for Express.js applications. Built with Socket.io and Chart.js to provide real-time server metrics with a clean, responsive interface.

This is a modernized version of express-status-monitor featuring:

  • 🔧 TypeScript support with full type definitions
  • 📦 ES Module syntax (ESM) support
  • 🚀 Modern JavaScript features and patterns
  • 📚 Improved documentation with comprehensive examples
  • 🎨 Enhanced UI with better responsiveness

Installation & setup

  1. Install the package:

    npm install @frozenjs/express-status-monitor
  2. Add to your Express application:

    import express from 'express';
    import { statusMonitor } from '@frozenjs/express-status-monitor';
    
    const app = express();
    
    // Add status monitor middleware BEFORE other routes
    app.use(statusMonitor());
    
    app.listen(3000, () => {
      console.log('Server running on http://localhost:3000');
      console.log('Status monitor available at http://localhost:3000/status');
    });
  3. Access the monitoring dashboard: Navigate to http://localhost:3000/status in your browser

Options

Monitor can be configured by passing options object into statusMonitor constructor.

Default config:

title: 'Express Status',  // Default title
theme: 'default.css',     // Default styles
path: '/status',
socketPath: '/socket.io', // In case you use a custom path
websocket: existingSocketIoInstance,
spans: [{
  interval: 1,            // Every second
  retention: 60           // Keep 60 datapoints in memory
}, {
  interval: 5,            // Every 5 seconds
  retention: 60
}, {
  interval: 15,           // Every 15 seconds
  retention: 60
}],
chartVisibility: {
  cpu: true,
  mem: true,
  load: true,
  eventLoop: true,
  heap: true,
  responseTime: true,
  rps: true,
  statusCodes: true
},
healthChecks: [],
ignoreStartsWith: '/admin'

Health Checks

You can add a series of health checks to the configuration that will appear below the other stats. The health check will be considered successful if the endpoint returns a 200 status code.

// config
healthChecks: [
  {
    protocol: 'http',
    host: 'localhost',
    path: '/admin/health/ex1',
    port: '3000',
  },
  {
    protocol: 'http',
    host: 'localhost',
    path: '/admin/health/ex2',
    port: '3000',
  },
];

Health Checks

Using module with socket.io in project

If you're using socket.io in your project, this module could break your project because this module by default will spawn its own socket.io instance. To mitigate that, fill websocket parameter with your main socket.io instance as well as port parameter.

License

MIT License © frozenjs