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

endpoint-tester

v0.1.1

Published

Auto-discover API endpoints and generate comprehensive test suites

Readme

endpoint-tester

Auto-discover API endpoints in your application and generate comprehensive test suites.

Install

npm install -g endpoint-tester

Usage

Scan for endpoints

endpoint-tester scan ./src --framework express
endpoint-tester scan ./src --framework express --output endpoints.json

Generate tests

endpoint-tester generate ./src --framework express --format vitest --output ./tests
endpoint-tester generate ./src --format jest --base-url http://localhost:8080

Options

| Option | Description | Default | | --------------- | ---------------------------------------- | ---------------------- | | --framework | Framework adapter (express, fastapi, spring) | express | | -o, --output | Output path — directory or file path | ./generated-tests | | --format | Test format (vitest, jest, pytest) | vitest | | --base-url | Base URL for test requests | http://localhost:3000|

The --output flag accepts either a directory or a specific file path:

# Output to a directory (file named endpoints.test.ts automatically)
endpoint-tester generate ./src --output ./tests

# Output to a specific file
endpoint-tester generate ./src --output ./tests/api.test.ts

Test formats: Jest vs Vitest

Both jest and vitest formats generate .ts test files. The key differences:

| Feature | Vitest | Jest | | ---------------- | ---------------------------------------------- | ----------------------------------------- | | Imports | Explicit import { describe, it, expect } | Uses globals (no import statement) | | File extension | .ts | .ts | | Config needed | vitest.config.ts | jest.config.ts with ts-jest or SWC | | Assertions | Method-specific status codes (toBe(201)) | Same |

Both formats now generate method-specific assertions (POST expects 201, DELETE expects 204, etc.), boundary value tests for path parameters, auth header tests, and error response tests for endpoints that accept a body.

Supported frameworks

  • Express.js - Detects app.get(), router.post(), route params, nested routers
  • FastAPI - Coming soon
  • Spring Boot - Coming soon

Programmatic API

import { Scanner, TestGenerator, ExpressAdapter } from "endpoint-tester";

const scanner = new Scanner(new ExpressAdapter());
const endpoints = await scanner.scan({ directory: "./src", framework: "express" });

const generator = new TestGenerator();
const tests = generator.generate({ endpoints, output: "./tests", format: "vitest" });

Contributing

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/my-feature)
  3. Commit your changes (git commit -am 'Add my feature')
  4. Push to the branch (git push origin feature/my-feature)
  5. Open a Pull Request

License

MIT