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

express-router-filesystem

v1.1.1

Published

Express FileSystem Router

Downloads

4

Readme

express-router-filesystem

Build Status Coverage Status NPM version Dependency Status devDependency Status

This module is a simple recursive filesystem reader that allows you to define routes in a filesystem structure.

Installation

$ npm install express-router-filesystem

or, using yarn

$ yarn add express-router-filesystem

Usage

const express = require('express');
const router = require('express-router-filesystem');

const app = express();

app.use(router({
  routesDir: __dirname + '/routes',
  routePrefix: '/api'
}));

app.listen(3000);

or using imports

import express from 'express';
import router from 'express-router-filesystem';

const app = express();

app.use(router({
  routesDir: __dirname + '/routes',
  routePrefix: '/api'
}));

app.listen(3000);

The route files

Export a function that takes the express router as an argument. The function name must be the method to match. The function should return the router.

// routes/users/get.js
module.exports = { 
  get(req, res) {
    res.send('GET /users');
  };
};

or using exports

// routes/users/get.js
export const get = (req, res) => {
  res.send('GET /users');
};

Named Params

Use brackets to assign a named parameter to a route. The value of the parameter will be available in the request object as req.params.<name>.

// routes/users/[id].js
module.exports = { 
  get(req, res) {
    res.send('GET /users, id ' + req.params.id);
  };
};

or using exports

// routes/users/[id].js
export const get = (req, res) => {
  res.send('GET /users, id ' + req.params.id);
};

Middlewares

You can define middlewares for a route by creating a file with the name _middleware.js. The file should export a default function that takes the express router as an argument. The function should return the router.

// routes/users/_middleware.js
module.exports = (req, res, next) => {
  console.log('middleware');
  next();
};

or using exports

// routes/users/_middleware.js
export default (req, res, next) => {
  console.log('middleware');
  next();
};

Any middleware defined in the _middleware.js file will be applied to all routes in the directory and its subdirectories. For example, if you have a route structure like this:

  • routes
    • _middleware.js (1)
    • users
      • _middleware.js (2)
      • [id].js
      • index.js
      • posts
        • _middleware.js (3)
        • [id].js
        • index.js

Calling /users/1 will call the middlewares numbers 1 and 2. Calling /users/posts/1 will call the middlewares numbers 1, 2 and 3.

You can also define multiple middlewares for a route by naming the file as _middleware.<name>.js. The name can be alphanumeric characters, - and _. Middlewares will be called in alphabetical order.

Examples:

  • _middleware.1-login.js
  • _middleware.session.js
  • _middleware.2_authorization_token.js

Options

routesDir

The absolute path to the directory containing the routes. This is required.

routePrefix

A prefix to add to all routes. This is optional.