npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@mewhhaha/little-router

v0.1.5

Published

`little-router` is a simple router for Cloudflare workers.

Downloads

25

Readme

Little Router

little-router is a simple router for Cloudflare workers.

  • Builder pattern
  • Typed route parameters
  • Async plugin system
  • Exposed type for routes that can be used with little-fetcher
  • Small size
import { Router } from "@mewhhaha/little-router";
import { ok } from "@mewhhaha/typed-response";

// Create a router instance using the builder pattern
const router = Router()
  // The other expected methods can be used here as well
  .get("/user/:id", [], async ({ params }) => {
    return ok(200, { message: `User: ${params.id}` });
  })
  // Special catch-all method, mostly for sending back a 404
  .all("/*", [], () => new Response(null, { status: 404 }));

Usage with Cloudflare workers

import { Router } from "@mewhhaha/little-router";
import { ok } from "@mewhhaha/typed-response";

type Env = {
  // Whatever your env is
  MY_STRING: string;
};

// In a worker the Env and the ExecutionContext will be
// passed along with the request.

// The rest parameters can be typed in the generic parameter like this.
const router = Router<[Env, ExecutionContext]>().get(
  "/user/:id",
  [],
  // The rest parameters will show up after the first object
  async ({ params }, env, ctx) => {
    const postUpdate = async () => {
      console.log("hello");
    };
    ctx.waitUntil(postUpdate());

    return ok(200, { message: env.MY_STRING });
  }
);

export default {
  fetch: router.handle,
};

Usage with fetcher

When combined with little-fetcher this gives you comprehensive way of doing server-client communication. Routes are generated from little-router which can then be consumed by little-fetcher which is essentially a wrapper that adds types to the fetch API or Durable Object stubs.

// Package: my-worker
import { Router } from "@mewhhaha/little-router";
import { ok } from "@mewhhaha/typed-response";

// A simple router that uses the @mewhhaha/typed-response package
const router = Router().get("/user/:id", [], async ({ params }) => {
  return ok(200, { message: `User: ${params.id}` });
});

// .infer is a non-value that has all the inferred route types
// If you want to shave off the complex type from the router
// you have to set it as an intermediate variable
const routes = router.infer;
export type Routes = typeof routes;

export default {
  fetch: router.handle,
};

// Package: my-application
import { Routes } from "my-worker";
import { fetcher } from "@mewhhaha/little-fetcher";

const worker = fetcher<Routes>("fetch", { base: "http://url-to-worker" });

// This has the same API as 'fetch' and returns typed responses if 'typed-response' was used
const response = await worker.get("/user/:id");

// Since we used 'ok' from typed-response then this is also typed
const { message } = await response.json();
//      ^ This has type `User: ${string}`

Usage with plugins

When combined with plugins you can set requirements on your routes and give hints to the fetcher. A route may have several plugins on it, and those are run asynchronously. If you want to synchronize several plugins you can just make an async plugin that coordinates the synchronous operations.

A common example of a plugin would be to create an authentication plugin.

// Package: my-plugin-auth

import { PluginContext, Plugin } from "@mewhhaha/little-router";
import { err } from "@mewhhaha/typed-response";

const validate = (authorization: string) => {
  if (authorization === "trust me bro") {
    return { valid: true, data: { username: "foobar" } } as const;
  }
  return { valid: false } as const;
};

const auth_ = ({
  request,
  // The PluginContext allows you to specify hints to the `little-fetcher` client
}: PluginContext<{
  init: {
    // These are just hints to the client and should always be validated
    headers: { Authorization: string } & Record<string, string>;
  };
}>) => {
  const authorization = request.headers.get("Authorization");
  if (!authorization) {
    // If a response is returned,
    // those will be added to the possible responses from this route
    return err(401, { message: "authorization_missing" });
  }

  const { valid, data } = validate(authorization);
  if (!valid) {
    return err(403, { message: "forbidden" });
  }

  // Anything returned from the plugin will be merged into
  // the first object in the route
  return { auth: data };
  // If a duplicate object is detected, then it will crash for safety's sake

  // The plugin can also be passed a generic parameter
  // if there are any rest parameters needed
  // eg. Plugin<[Env, ExecutionContext]>
} satisfies Plugin;

// Package: my-worker
import { auth_ } from "my-plugin-auth";
import { Router } from "@mewhhaha/little-router";
import { ok } from "@mewhhaha/typed-response";

// The auth_ plugin is added to the array in the route
// Any number of plugins can be added in the array
const router = Router().get("/user/:id", [auth_], async ({ params, auth }) => {
  // We now have the data `auth` that we returned from the plugin
  return ok(200, { message: `User: ${auth.username}` });
});

const routes = router.infer;
export type Routes = typeof routes;

// Package: my-application
import { Routes } from "my-worker";
import { fetcher } from "@mewhhaha/little-fetcher";

const worker = fetcher<Routes>("fetch", { base: "http://url-to-worker" });

const response = await worker.get("/user/:id", {
        // This is now a required header because of the hint in the plugin
        headers: { "Authorization": "trust-me-bro" }
    });

Usage with Durable Objects

Here's an example of how to use the router with a Durable Object. You can either create the router outside of the class or create it internally as a static value.

// Package: my-worker
import { Router } from "@mewhhaha/little-router";
import { ok } from "@mewhhaha/typed-response";

export class DurableObjectTest implements DurableObject {
  count: number;

  static router = Router<DurableObjectTest>()
    .post("/increment", [], (_, self) => {
      self.count++;
      return ok(200, { count: self.count });
    })
    .post("/decrement", [], (_, self) => {
      self.count--;
      return ok(200, { count: self.count });
    });

  fetch(request) {
    return DurableObjectTest.router(request, this);
  }
}

const routes = DurableObjectTest.router.infer;
type Routes = typeof routes;

type Env = {
  // The namespace corresponding to the durable object
  DO_TEST: DurableObjectNamespace;
};

export default {
  fetch: (request: Request, env: Env) => {
    const stub = env.DO_TEST.get(env.DO_TEST.idFromName("foobar"));
    // Just pass the fetcher the stub with the routes
    const test = fetcher<Routes>(stub);

    await test.post("/increment");
    await test.post("/decrement");
  },
};