Composable trie based router
Composable trie based router. It's faster than traditional, linear, regular expression-matching routers, although insignficantly, and scales with the number of routes.
$ npm install wayfarer
const wayfarer =const router =routerrouterrouter// => 'user is tobi'// => '404 not found'
Routers can be infinitely nested, allowing routing to be scoped per view. Matched params are passed into subrouters. Nested routes will call their parent's default handler if no path matches.
const r1 =const r2 =r2r1// => 'subrouter trix!'
Initialize a router with a default route. Doesn't ignore querystrings and hashes.
Register a new route. The order in which routes are registered does not matter. Routes can register multiple callbacks. The callback can return values when called.
Match a route and execute the corresponding callback. Alias:
Returns a values from the matched route (e.g. useful for streams). Any
additional values will be passed to the matched route.
Wayfarer is built on an internal trie structure. If you want to build a router
using this trie structure it can be accessed through
require('wayfarer/trie'). It exposes the following methods:
trie = Trie()- create a new trie
node = trie.create(route)- create a node at a path, and return a node
node = trie.match(route)- match a route on the the trie and return a node
trie.mount(path, trie)- mount a trie onto a node at route
/:foo/:bar/:baz won't work. This is due
Trie.mount() overriding child
partial paths when mounted. I'll get around to fixing this at some point in the
future, but if anyone wants to contribute a patch it'd most appreciated.
Routers like react-router are complicated solutions for a simple problem. In reality all that's needed is a methodless router that can define + match paths and can mount other routers to delegate requests.
Wayfarer only compares strings. Before you pass in an url you probably want to strip it of querystrings and hashes using the pathname-match module.