🖲️ @bronti/wooter

Warning

wooter is beta & WIP, the main features are implemented but there are some bugs that may appear. I advise against using this for big influential projects until v100.0.0
woot around and find out

Note

wooter uses epoch semver.

wooter is a simple TypeScript router library, it's inspired by Sveltekit's router, as well as Oak and Hono.

• 🔁 Promise-based responses: responses are returned via a seperate promise, rather than a return from the route function's promise. This is useful for doing extra after responding.
• 🔌 Plug-and-play: wooter doesn't implement any server implementation directly. Instead, a fetch method is implemented, meaning wooter works anywhere where the fetch API is available, allowing you to plug it into any existing HTTP server implementations, or use it virtually by not adding a server.
• 🧠 Smart type-safe paths: wooter uses chemin for route matching, a function based pattern builder for routes.
• 🔗 Middleware: wooter includes a middleware system that is just as innovative as it's routing capabilities.

Deno Example

import { delay } from "jsr:@std/async"
import { c, Wooter } from "jsr:@bronti/wooter"

const wooter = new Wooter()

wooter.route(c.chemin(), "GET", ({ resp }) => {
	resp(new Response("hi"))
})

wooter.route(c.chemin("error"), "GET", ({ resp }) => {
	resp(new Response("An error occured!!", { status: 500 }))
})

wooter.route(
	c.chemin("with", c.pNumber("param")),
	"GET",
	({ resp, params }) => {
		resp(new Response(`hi ${params.get("param")}`))
	},
)

wooter.route(c.chemin("after"), "GET", async ({ resp }) => {
	resp(new Response("ok!"))
	await delay(400)
	console.log("this ran after the response was sent.")
})

export default wooter