New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

swork-router

Package Overview
Dependencies
Maintainers
1
Versions
12
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

swork-router

Router using the swork framework.

  • 1.3.3
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
3
decreased by-25%
Maintainers
1
Weekly downloads
 
Created
Source

swork-router

npm travis ci coverage download Greenkeeper badge

swork-router is router middleware for swork powered by path-to-regexp. It is built with TypeScript and async methods.

License

MIT

Installation

npm install swork-router

yarn add swork-router

Example

import { Swork, FetchContext } from "swork";
import { Router } from "swork-router";

const app = new Swork();
const router = new Router();

router.get("/hello/:id", (context: FetchContext) => {
    context.response = new Response(`world id: ${context.params.id}`);
});

app.use(router.routes());

app.listen();

Methods

get | post | put | patch | delete | head | options | all

Create a route using the HTTP verb as your method name such as router.get(...) or router.post(...). In addition, all is available to match on all HTTP verbs.

router.get("/foos", async (context: FetchContext, next: () => Promise<void>) => {
    // manipulate request
    const response = await next();
    // manipulate or cache response
    context.response = response;
});

You are able to pass in a single path or an array of paths with the middleware to be invoked when a path is matched.

router.get(["/foos", "/foos/:id"], (context) => {...});

Every verb method returns the router instance allowing chaining of path handlers.

router
    .get("/foos", (context) => {...})
    .post("/foos", (context) => {...})
    .all("/foos/:id", (context) => {...});

Route paths must start with a slash and end without one. Paths are translated to regular expressions using path-to-regexp. As a result, query strings are not evaluated when matching requests.

use

use allows the nesting of routers. This is useful when building a routes in a separate module.

const router = new Router({ prefix: "/api" });

router.use(getFooApiRouter());
router.use(getBarApiRouter());

app.use(router.routes());

Configuration

Prefix

Routes can be prefixed at the router level.

const router = new Router({
    prefix: "/foos"
});

router.get("/", ...); // responds to "/foos"
router.put("/:id", ...); // responds to "/foos/:id"

Origin

Alternate origins can be used but default to configuration.origin from swork.

const router = new Router({
    origin: "https://www.hello.com"
});

router.get("/world", () => { ... });

Url Parameters

Named route parameters are captured and added to context.params property.

router.put("/:id/:name", (context: FetchContext) => {
    console.log(context.params);
    // => { id: 99, name: "Jane" }
});

Contact

If you are using swork or any of its related middlewares, please let me know on gitter. I am always looking for feedback or additional middleware ideas.

Keywords

FAQs

Package last updated on 08 Jan 2020

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc