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

@spotlightjs/sidecar

v2.5.0

Published

A small proxy server to capture and forward data from backend services to Spotlight.

Readme

Spotlight Sidecar

The Spotlight Sidecar is a small proxy server that allows (development) servers to send data to Spotlight.

Installation

npm install @spotlightjs/sidecar

Usage

As a Library

import { setupSidecar } from '@spotlightjs/sidecar';

// When you start your dev server
await setupSidecar();

As a CLI

# Start with default settings (port 8969)
spotlight-sidecar

# Start on a custom port
spotlight-sidecar --port 3000
# or
spotlight-sidecar -p 3000

# Enable debug logging
spotlight-sidecar --debug
# or
spotlight-sidecar -d

# Combine options
spotlight-sidecar --port 3000 --debug

# Show help
spotlight-sidecar --help

CLI Options

  • -p, --port <port> - Port to listen on (default: 8969)
  • -d, --debug - Enable debug logging
  • -h, --help - Show help message

MCP (Model Context Protocol) Integration

Spotlight Sidecar includes MCP tools for accessing local debugging data through Claude Code and other MCP clients.

Available Tools

Error Debugging

  • search_errors - Retrieve recent application errors with stack traces
  • search_logs - Access application logs for behavior analysis

Performance & Tracing

  • search_traces - List recent traces with performance summaries
  • get_traces - Get detailed span tree and timing for specific traces

Trace Viewing Workflow

  1. List Recent Traces

    Use search_traces to see trace summaries:
    - Trace IDs (first 8 characters shown)
    - Root transaction names  
    - Duration and span counts
    - Error counts per trace
    - Timestamps for debugging specific periods
  2. Examine Specific Trace

    Use get_traces with a trace ID:
    - Complete hierarchical span tree
    - Individual span durations and operations
    - Error context within trace timeline
    - Chronological flow of operations

Prerequisites

To see trace data, ensure your application has:

  • Sentry SDK with performance monitoring enabled
  • Transaction instrumentation generating trace events
  • Recent activity that creates spans (API calls, database queries, etc.)

Example Usage

# Start sidecar with debug logging to see trace data flow
spotlight-sidecar --debug

# In Claude Code or MCP client:
# 1. List recent traces
search_traces({ filters: { timeWindow: 300 } })

# 2. Get details for a specific trace
get_traces({ traceId: "71a8c5e4" })