## The problem
A route feels slow. What do you do? Usually console.log(Date.now()) around
the code, or open a separate dashboard, or hit the route a few times in
Postman and try to eyeball the difference. It works but it's slow and
disconnected from the actual code.
## What I'm building
API Performance Profiler. An open-source tool that shows real API latency
inline in VS Code, right next to the route.
@get('/users') 🟢 84ms
@get('/products') 🟡 430ms
@get('/orders') 🔴 1.82s
No dashboard. No cloud account. No API key. It runs on your machine and
watches real traffic as it comes in.
## Why local first
I don't want a tool that needs a signup and a config file just to tell me
one route is slow. So it works offline:
- Your backend runs locally like normal
- A small middleware measures real request timings
- VS Code reads that data and shows it next to your code
Nothing leaves your machine.
What it supports first
Node.js and TypeScript. Express and NestJS to start.
Only real metrics. Average latency, P50/P95/P99, throughput, error rate.
If there isn't enough traffic yet it just says so instead of showing a
fake number.
## What's next
Database query timing. External HTTP call breakdowns. A CLI for people who
don't use VS Code. Later, something for teams to see this data together.
## Follow along
Building this in public and posting updates here as it comes together.
Repo isn't public yet but will be soon, and I'd love contributors once it
is (issues, ideas, PRs).
If this is something you'd use, follow along. And let me know in the
comments if there's a framework you'd want supported first.
Top comments (0)