(pronounced "zinc")
xink's unique feature is that it's a directory-based router. Think Next's App router or SvelteKit routing. And since this is for APIs, each route file should export functions named after HTTP methods in order to define your route handlers (e.g. GET).
I like using this in SvelteKit, and since I couldn't really find an API-only router that uses a similar strategy, I decided to put something together.
xink is in the alpha stage (maybe beta??) and I'm looking for contributors to help make it better. I currently only code as a hobby, so I'm sure there are some areas that need improvement, fixing, or some major thing(s) I've overlooked.