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

@epicdm/flowstate-obs-middleware

v1.0.0

Published

Express middleware for Epic FlowState observability integration

Downloads

206

Readme

@epicdm/flowstate-obs-middleware

Express middleware for Epic FlowState observability integration.

Installation

yarn add @epicdm/flowstate-obs-middleware

Quick Start

import express from 'express';
import { createObsMiddleware } from '@epicdm/flowstate-obs-middleware';

const app = express();

// Create middleware suite
const obs = createObsMiddleware({
  projectId: 'my-service',
  serviceName: 'My Service',
  version: '1.0.0',
});

// Attach middleware (order matters!)
app.use(obs.asyncContext);    // First: sets up request context
app.use(obs.requestLogger);   // Second: logs requests

// Your routes here
app.get('/api/data', (req, res) => {
  obs.logger.info('Fetching data', { userId: req.user?.id });
  res.json({ data: [] });
});

// Health check endpoint
app.get('/health', obs.healthCheck());

// Error handler must be last
app.use(obs.errorHandler);

app.listen(3000, () => {
  obs.logger.info('Server started', { port: 3000 });
});

Configuration

Environment Variables

| Variable | Default | Description | |----------|---------|-------------| | OBS_SERVER_URL | http://obs-server:8080 | Observability server URL | | OBS_API_KEY | - | API key for authentication | | OBS_LOG_LEVEL | info (dev) / error (prod) | Minimum log level | | OBS_ENABLED | true | Enable/disable observability | | OBS_BATCH_SIZE | 10 | Logs to batch before sending | | OBS_FLUSH_INTERVAL | 5000 | Max ms before flush | | NODE_ENV | development | Controls default log level |

Options

createObsMiddleware({
  projectId: 'my-service',      // Required: unique service identifier
  serviceName: 'My Service',    // Optional: human-readable name
  version: '1.0.0',             // Optional: service version
});

Features

Async Context

Request context is automatically propagated through async operations:

app.get('/api/users/:id', async (req, res) => {
  // Logger automatically includes requestId, traceId, etc.
  obs.logger.info('Fetching user');

  const user = await fetchUser(req.params.id);

  // Even in nested async calls
  obs.logger.info('User fetched', { userId: user.id });

  res.json(user);
});

Request Logging

All HTTP requests are automatically logged with:

  • Method, path, status code
  • Response time
  • Request ID for correlation

Health check endpoints (/health, /healthz, etc.) are excluded.

Error Handling

Unhandled errors are:

  • Logged to console with full context
  • Sent to obs-server (if configured)
  • Returned as 500 response with requestId

Health Checks

app.get('/health', obs.healthCheck({
  customChecks: [
    {
      name: 'database',
      check: async () => ({
        healthy: await db.ping(),
        details: { connections: db.poolSize },
      }),
    },
  ],
}));

License

Apache-2.0