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-route-boilerplate

v1.0.3

Published

Boilerplate code for Express application with easy wiring of routes and middlware

Downloads

11

Readme

express-route-boilerplate

Boilerplate code for an Express application which allows to write express routes/middlware easily and faster.

How to add

Install express-route-bootstrap

npm i express-route-boilerplate

Add to your application

const initExpress = require('express-route-boilerplate');

How to use

Define the routes in your application as modules in js files. FileName will be a route in the application.

// v1.js

const express = require('express');
const routes = express.Router();

router.get('/', (req, res) => { ... }); //  GET /v1/
router.post('/', (req, res) => { ... }); // POST /v1/
router.get('/version', (req, res) => { ... }); // GET /v1/version/

module.exports = routes;

//root.js 

const express = require('express');
const routes = express.Router();

router.get('/', (req, res) => { ... });

module.exports = routes'

...

Define application level middlwares

// logger.js

const logger = (req, res, next) => {
  // Logging
  next();
}

module.exports = { logger };

// auth.js

const auth = (req, res, next) => { ... }

const validate = (req, res, next) => { ... }

module.exports = { auth, validate };

Place the routes and middleware in separate directories (example given below)

.
├── routes
│   ├── root.js
│   ├── v1.js
├── middleware
│   ├── logger.js
│   ├── auth.js
├── index.js
.
.
.

In the entrypoint file, invoke the module

// index.js 

const initExpress = require('express-route-boilerplate'); // Import

....


initExpress({ pathToRoutes: './routes/', pathToMiddleware: './middleware/',
    port: 5000, listenCallback: () => {console.log('app started')}}); // Invoke

API Reference

Method invocation

initExpress({ pathToRoutes, pathToMiddleware, rootRouteName, port, listenCallback });

Parameters

| Parameter | Type | Required (default) | Usage | Example | | --- | --- | --- | --- | --- | | pathToRoutes | string | yes (N/A) | Relative path from root of the application to routes directory | ./routes/ | | pathToMiddleware | string | no (N/A) |Relative path from root of the application to middlware directory | ./middlware/| | rootRouteName | string | no (root) | Routes define in this file will become root (/) level routes without fileName prefix | root| | port | number | no (3000) | Port the application should run in | 5000 | | listenCallback | function | no | Callback to be passed to express().listen | () => { console.log('App started');

IMPORTANT

Make sure pathToRoutes and pathToMiddleware has ending / charater as given in example above.