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

moped-router

v3.0.0

Published

Router for a moped application

Downloads

3

Readme

moped-router

Router for a moped application

Build Status Dependency Status NPM version

Installation

npm install moped-router

Usage

moped-router can be used as a standalone router. It can handle being given any aribrary Object with a "path" property, which will be treated as the moped request.

cars.js

var MopedRouter = require('moped-router');
var app = new MopedRouter();

app.get('/user/:id', function (req) {
  return db.users.find({_id: req.params.id});
});

var carApp = new MopedRouter();
var cars = {
  volvo: {color: 'red', size: 'big'},
  bmw: {color: 'black', size: 'small'}
};
carApp.get('/color', function (req) {
  return cars[req.params.car].color;
});
carApp.get('/size', function (req) {
  return cars[req.params.car].size;
});
app.use('/car/:car', carApp);

app.handle({method: 'get', path: '/car/volvo/color'}).then(function (res) {
  assert(res == 'red');
});

module.exports = app;

API

app.use(path?, subapp)

app.use lets you mount sub-applications. You may provide an optional base-path for the sub-application (which defaults to /). This path is a string, and does not get pattern matching like other paths.

app.METHOD(path, handlers...)

Register a handler that is called for each request that has the given METHOD and path (using express style path matching). These can be made asynchronous by returning promises.

app.all(path, handlers...)

Just like app.METHOD(path, handlers...) except for it targets every method.

app.handle(request, ...)

Handle a request and get a promise for the results

Moped Extensions / Changes

Moped provides a .run method that behaves differently depending on whether it is on the client or the server. It also passes in req and res with some helpful methods and properties.

License

MIT