Launching: @wthek/fastify-middleware & @wthek/nestjs-middleware
Published on June 2, 2025 by Skillnter
We’re excited to officially open support for two modular middleware projects under the WTHek Collective — designed to help backend developers move faster with fewer headaches.
🧩 @wthek/fastify-middleware
This package is all about DX-first Fastify development — starting with production-friendly middleware that removes boilerplate, encourages best practices, and works out of the box.
✅ Clean error handling
✅ Middleware composition helpers
✅ Built-in TypeScript types
✅ Sensible defaults that don’t get in your way
It’s lean, extensible, and built for teams who want to move fast without skipping the fundamentals.
📦 View on npm
✅ Clean error handling
✅ Middleware composition helpers
✅ Built-in TypeScript types
✅ Sensible defaults that don’t get in your way
It’s lean, extensible, and built for teams who want to move fast without skipping the fundamentals.
📦 View on npm
🛠️ @wthek/nestjs-middleware — for both Express and Fastify setups
Most NestJS middleware tools assume you're using Express. Ours doesn’t.
@wthek/nestjs-middleware is built to support both HTTP engines — Express and Fastify — out of the box. You don’t need to choose or refactor to switch engines later.
✅ Compatible with both Express and Fastify
✅ Structured error handling
✅ Lightweight and framework-aligned
✅ Ready for deeper DX and logging features
✅ Structured error handling
✅ Lightweight and framework-aligned
✅ Ready for deeper DX and logging features
This means whether you're starting with Express or migrating to Fastify for performance, your middleware stack can stay consistent.
💡 Why This Matters
Middleware shouldn’t be an afterthought — it’s where performance, security, and developer sanity all meet. Our mission is to make clean, modular backend patterns easier to adopt for everyone, whether you're building a startup or contributing to OSS.
❤️ How You Can Help
If you believe in open tooling that prioritizes developer experience, you can support us by:
- Backing this Collective
- Sharing our projects with other devs
- Opening issues, PRs, or feedback threads
- Helping us expand documentation and real-world examples
Every contribution — financial or otherwise — helps us build middleware that truly supports modern backend work.
Thanks for being part of the journey.