router-benchmark VS express-ts-handler

I got the point of it, but it's really hard to do by just reading the readme. Here I found different routers to compare with, there are two kinds: frameworks like express, fastify, and second kind is framework-independent routers like find-my-way. Routup isn't the first case - not a framework, and not the second case - does more than just a router, so it's somewhere in between.

For static routes e.g. /help or /about, these are loaded into a radix tree structure. There are expensive (memory wise), but still fast when resolving the handler. You can look at benchmarks of popular router implementations and see how they fare with large amounts of static routes.

Check out my library: https://github.com/romeerez/express-ts-handler, it tells right in the beginning and as obvious as possible what is it for, and what it does, the readme is compact for those who tl;dr, and contains simple examples. And still - zero interest from the community! Even though I've made it not for myself, but because of being tired to see how people forgot to validate params all the time, or doing it in a not type-safe way where it's easy to make mistakes and they actually making mistakes because of this.

It has a descriptive readme with examples, it has example code, I thought it is clear what it is for. It's inspired by the fact that most Express code boilerplates and various examples have no type safety after validation, and no return type checks, even though it is a public interface and it is important to be safe. Typically people use middleware to set data to req without TS knowing about it. So I created this lib to fix this.