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-enhanced-router

v1.0.7

Published

Gives express.js router Infrastructure that it deserves

Downloads

13

Readme

express-enhanced-router

Gives express.js router Infrastructure that it deserves

Usage

npm install --save express-enhanced-router

Create those dirs at root of your project

if you prefer putting infrastructure folder to subdirectory, you need to provide it's name as second parameter to this module constructor

  • infrastructure/controllers
  • infrastructure/factories
  • infrastructure/services

Controllers

Those are needed for handling your requests, action methods are expected to return Promise

Create infrastructure/controllers/test.controller.js

class TestController {
    static $inject() { return ['TestService']; } // return list of injectable from your service folder
    static $actions() { return ['getFoo']; } // return list of your controller's actions
    getFoo(request, response) {
        return this.testService.foo()
    }
}
module.exports = { TestController };

Providers

Those are just functions that provides entities for Dependency Injection

Create infrastructure/providers/test.provider.js


function TestProvider() {
  const test = {
    var1: 1,
    var2: 2,
  };
  return test;
}

module.exports = {
  TestProvider
};

Services

Those are your Dependency Injection enabled Services

Create infrastructure/services/test.service.js


class TestService {
    static $inject() { return ['test']; } // this will hook up TestProvider
    foo() {
        return new Promise((resolve, reject) => {
            resolve({
                result: 'fooResult',
                ...this.test
            })
        })
    }
}

module.exports = { TestService };

index.js

const express = require('express');
const enhancedRouter = require('express-enhanced-router');

const app = express();

const router = express.Router();

/**
 * you can pass subdirectory name
 * as second param if infrastructure
 * folder is not in your project root
 *
 * app.use(enhancedRouter(router, 'sub_dir'));
 */

app.use(enhancedRouter(router));

app.listen(3000, (err) => {
    console.log('Listening at port 3000 ...');
})

That's IT