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

@evalview/node

v0.3.2

Published

Drop-in Node.js middleware for EvalView — the open-source regression testing framework for AI agents. Golden baseline diffing and CI/CD integration for LangGraph, CrewAI, OpenAI, and Anthropic agents.

Readme

@evalview/node — Proof that your agent still works.

You changed a prompt. Swapped a model. Updated a tool. Did anything break? Run EvalView. Know for sure.

Drop-in Node.js/Next.js middleware for EvalView — the regression testing framework for AI agents.


What EvalView Catches

| Status | What it means | What you do | |--------|--------------|-------------| | ✅ PASSED | Agent behavior matches baseline | Ship with confidence | | ⚠️ TOOLS_CHANGED | Agent is calling different tools | Review the diff | | ⚠️ OUTPUT_CHANGED | Same tools, output quality shifted | Review the diff | | ❌ REGRESSION | Score dropped significantly | Fix before shipping |


Quick Start

npm install @evalview/node
pip install evalview

Next.js App Router

// app/api/evalview/route.ts
import { createEvalViewMiddleware } from '@evalview/node';

export const POST = createEvalViewMiddleware({
  targetEndpoint: '/api/your-agent',
});

Express.js

const { createEvalViewMiddleware } = require('@evalview/node');

app.post('/api/evalview', createEvalViewMiddleware({
  targetEndpoint: '/api/your-agent',
}));

Then point EvalView at your endpoint:

# .evalview/config.yaml
adapter: http
endpoint: http://localhost:3000/api/evalview

Capture baseline and check for regressions:

evalview snapshot   # save current behavior as baseline
evalview check      # detect regressions on every change

Claude Code Integration (MCP)

Test your agent without leaving the conversation:

claude mcp add --transport stdio evalview -- evalview mcp serve
cp CLAUDE.md.example CLAUDE.md

Ask Claude Code naturally:

You: Did my refactor break anything?
Claude: [run_check] ✨ All clean! No regressions detected.

You: Add a test for my weather agent
Claude: [create_test] ✅ Created tests/weather-lookup.yaml
        [run_snapshot] 📸 Baseline captured.

No YAML. No terminal switching. No context loss.

Full MCP docs →


Configuration

createEvalViewMiddleware({
  // Required: your agent's endpoint
  targetEndpoint: '/api/your-agent',

  // Optional: default user ID for test requests
  defaultUserId: 'your-dev-user-id',

  // Optional: dynamic user ID resolution
  getUserId: async (req) => {
    const user = await findOrCreateUser('[email protected]');
    return user.id;
  },

  // Optional: transform EvalView request to your API format
  transformRequest: (req) => ({
    message: req.query,
    userId: req.context?.userId,
  }),

  // Optional: parse your API response to EvalView format
  parseResponse: (responseText, startTime) => ({
    session_id: `session-${startTime}`,
    output: '...',
    steps: [...],
    cost: 0.05,
    latency: Date.now() - startTime,
  }),
});

Automate It

# .github/workflows/evalview.yml
- run: evalview check --fail-on REGRESSION --json
  env:
    OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}

Documentation

Full docs →Examples →Issues →


License

Apache-2.0