It’s been just a few weeks since the last milestone, but TriFrost has grown sharper in all the right ways. The internal skeleton is solid. The routing engine is fast, predictable, and expressive. Middleware composition is clean. Context handling is robust. But more importantly — the surrounding world is starting to notice.
This post isn’t about hitting numbers (though we’ll mention them). It’s about direction. Intent. And the quiet confidence that comes from a system starting to show its final form.
Docs that don't hide the wiring
We’ve crossed the 50% mark on documentation, not just in terms of quantity, but in the kind of clarity that teaches, not distracts. No fluff, no “magic happens here.” The docs tell you what happens, why it happens, and exactly how to trace it.
From request lifecycle to JSX rendering, every core system has an explanation you can trust — because TriFrost was never about hiding complexity. It’s about owning it, and then giving you the handles to shape it.
75%+ Coverage
Tests aren’t vanity metrics, they’re guardrails against accidental complexity. And as of this week, we’ve passed 75% coverage.
But what really matters is what those tests revealed:
- Subtle bugs in middleware error propagation
- Timing edge cases with .abort() and .setStatus()
- Early inconsistencies in route fallback chaining
All of those are fixed now. And the suite keeps growing — because confidence should be earned, not assumed.
⭐ 17 Stars
TriFrost has quietly crossed 17 stars on GitHub — all organic, no SEO plays. Just people finding it, liking what they see, and clicking the button.
That’s the best kind of validation: the unexpected kind.
It's you we're building this for.
🚀 What’s Landed
Since the last checkpoint:
- ❄️ Middleware chaining now reflects your mental model exactly — no more guessing where .use() lands
- ❄️ ctx.html, ctx.json, and friends now respect prior status codes
- ❄️ Style rendering is now more ergonomic than ever
- ❄️ Internal log scrambling to keep your logs secret-free
- ❄️ Nonce-behavior within Security Middleware
- ❄️ Fallback logic detects “silent” errors and redirects to .onError() or .onNotFound() correctly
Every improvement has moved us closer to a system you can reason about — and rely on.
🔬 A Note on Benchmarks
In our last benchmark, TriFrost handled around 151k requests/sec on average, already outperforming Koa and Express with ease, and going toe-to-toe with Elysia and Hono.
But with recent routing and perf, that number’s now up to 156k req/sec, a measurable +3% throughput gain — with lower max latency and tighter spread.
Benchmarking TriFrost at http://localhost:3001
┌─────────┬──────┬──────┬───────┬───────┬────────┬─────────┬───────┐
│ Stat │ 2.5% │ 50% │ 97.5% │ 99% │ Avg │ Stdev │ Max │
├─────────┼──────┼──────┼───────┼───────┼────────┼─────────┼───────┤
│ Latency │ 4 ms │ 5 ms │ 11 ms │ 12 ms │ 5.9 ms │ 1.79 ms │ 53 ms │
└─────────┴──────┴──────┴───────┴───────┴────────┴─────────┴───────┘
┌───────────┬─────────┬─────────┬─────────┬─────────┬─────────┬──────────┬─────────┐
│ Stat │ 1% │ 2.5% │ 50% │ 97.5% │ Avg │ Stdev │ Min │
├───────────┼─────────┼─────────┼─────────┼─────────┼─────────┼──────────┼─────────┤
│ Req/Sec │ 143,999 │ 143,999 │ 156,671 │ 159,999 │ 156,224 │ 4,254.92 │ 143,880 │
├───────────┼─────────┼─────────┼─────────┼─────────┼─────────┼──────────┼─────────┤
│ Bytes/Sec │ 16.3 MB │ 16.3 MB │ 17.7 MB │ 18.1 MB │ 17.7 MB │ 484 kB │ 16.3 MB │
└───────────┴─────────┴─────────┴─────────┴─────────┴─────────┴──────────┴─────────┘
Req/Bytes counts sampled once per second.
# of samples: 10
1563k requests in 10.04s, 177 MB read
We’re not playing the numbers game — but it’s nice when the numbers agree.
And unlike some micro frameworks, TriFrost does this with:
- structured context tracking
- typed middleware
- observability hooks
- built-in auth and cache
- ...
Fast and thoughtful — that’s the bar.
ps: We have some more ideas ;) but that's for later.
🙏 Call to Action
If you're the kind of developer who wants to understand what your framework is doing — who doesn’t want to “just trust the magic” — TriFrost is for you.
- ⭐ Star the repo — it helps more than you think
- 📦 Try it:
npm install @trifrost/core
And yeah — the Discord’s quiet (🥲). But we’re still there. Waiting. Building. Iterating. ❄️
TriFrost isn’t trying to be the loudest voice in the room. It’s trying to be the most reliable.
The one:
- you reach for when you want performance and composability.
- that respects your time, your brain, and your environment.
- that stays out of your way, until you need it to get out in front.
We’re just getting started. And we’re glad you’re here.