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

trafico

v1.0.8

Published

The most awesome router for Express.

Downloads

144

Readme

npm version Downloads Build Status Coverage Status codebeat badge Greenkeeper badge

🚥 Awesome -zero dependency- router for Express.

Tráfico will map routes to controllers and enable them in your Express application, so you don't have to do it manually and for each one. This provides an easier abstraction and enables a drop-in-and-use route/controller setup.

Basic use

const express = require('express');
const Trafico = require('trafico');

const app = express();
const trafico = new Trafico({
  express,
  routes: `/path/to/routes`,
  controllers: `/path/to/controllers`
});

app.use(trafico.route());
app.listen(port, () => {
  console.log(`Up on port: ${port}`);
});

Routes

In your routes folder (/path/to/routes) create the routes you need to be mapped to your application. For example:

| path/to/routes
  | home.js
  | user.js

The home.js route would look similar to this (define your routes as you normally would in your Express application):

module.exports = (router, controller) => {
  router.get('/', controller.index);
  router.get('/date', controller.date);

  return router;
};

Controllers

Tráfico will load all routes from the routes path you specify and try to look for the controllers to match them. Create your controllers in the controllers folder (/path/to/controllers). Controllers must be named like their corresponding routes.

| path/to/controllers
  | home.js
  | user.js

The home.js controller would expose the methods mapped in the route:

module.exports = {
  index: (req, res) => {
    res.send({ hello: 'world' });
  },
  
  date: (req, res) => {
    res.send({ date: +new Date() });
  }
};

Working examples

Have a look at the /test folder. ExpressBoilerplate also uses Tráfico.

Contribute

fork https://github.com/aichholzer/trafico

License

MIT