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

@felmonon/msw-inspector

v0.1.2

Published

Find gaps between your MSW handlers and your actual API usage.

Readme

msw-inspector

Find gaps in your API mock coverage before they reach CI.

MSW handlers drift. API calls get added without mocks, and old mocks stay behind after the code moves on. msw-inspector scans both sides, compares them, and reports what is covered, what is not, and what looks stale.

Install

npm install -D @felmonon/msw-inspector

CLI

Run it from the project root:

npx msw-inspector

Or run it without installing first:

npx @felmonon/msw-inspector

Useful flags:

npx msw-inspector \
  --handlers "src/**/*.{ts,tsx,js,jsx,mts,mjs,cjs}" \
  --sources "src/**/*.{ts,tsx,js,jsx,mts,mjs,cjs}" \
  --exclude "**/dist/**" "**/*.d.ts" \
  --report-file msw-inspector.json \
  --format text

The CLI prints a human-readable summary by default. Use --format json when you want the full report for CI or a downstream action.

Output

Text output looks like this:

✓ 23 handlers found
✓ 31 API calls found
✗ 8 unmocked endpoints
✗ 3 stale mocks

Coverage: 74% (23/31)

The JSON report written by --report-file includes:

{
  "schemaVersion": 1,
  "summary": {
    "mockedCalls": 23,
    "totalCalls": 31,
    "usedHandlers": 20,
    "totalHandlers": 23,
    "staleHandlers": 3,
    "unmockedCalls": 8,
    "percentage": 74.2
  }
}

Supported patterns

The first release is intentionally narrow:

  • msw http.* handlers
  • legacy msw rest.* handlers
  • handler matchers from string literals, static template literals, static consts, new URL(...).href, new URL(...).toString(), and String(new URL(...))
  • fetch(...), window.fetch(...), globalThis.fetch(...)
  • common axios call shapes, including axios.get(...), axios.request(...), axios(...), and same-file axios.create(...) instances

GitHub Action

The repo ships with a thin GitHub Action wrapper. It reads the JSON report that the CLI already produced, writes a job summary, and can optionally upsert one sticky PR comment.

Because the repository includes action.yml and branding metadata, you can publish this Action to the GitHub Marketplace once you cut a tagged release.

name: msw coverage

on:
  pull_request:
  push:

jobs:
  inspect:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - run: npm ci
      - run: npx msw-inspector --report-file msw-inspector.json --format json
      - uses: felmonon/msw-inspector@v1
        with:
          summary-file: msw-inspector.json
          comment: true

The action does not compute a baseline delta yet. It publishes the current report cleanly and predictably.

Limitations

  • It does not try to infer custom wrapper helpers.
  • It does not resolve cross-file constants or imported axios instances.
  • It does not analyze GraphQL, WebSocket, or SSE handlers.
  • It reports dynamic or ambiguous patterns as unsupported instead of guessing.

Local Development

npm install
npm test
npm run typecheck
npm run build

If you are changing the scanning logic, keep the test fixtures small and explicit. The tool is more useful when it stays opinionated.