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 🙏

© 2026 – Pkg Stats / Ryan Hefner

express-sledge

v0.0.2

Published

a simple way to config url,controller,view of express based web app

Readme

express-sledge

Build Status

A simple way to config URL , Controller , View of express based web app

how to use

  • write a config file router.json , config url,controller,view

	{
    	"/": {
        	"action": "index",
        	"method": "execute",
        	"result": {
            	"success": "/view/index.jade",
            	"error": "/view/error.jade"
        	}
    	},
    	"/product": {
            "subs": {
                "/intro": {
                    "action": "product/intro",
                    "result": {
                        "success": "/view/product/intro.jade",
                        "error": "/view/product/error.jade"
                    }
                },
                "/:productId": {
                    "action": "product/detail",
                    "result": {
                        "success": "/view/product/detail.jade"
                    }
                }
            }
        }
    }
  • in app.js

      
        var sledge = require("express-sledge");
    	sledge(app, require("./router.json"),path.join(__dirname, "routes"));
      
  • write a controller , index.js

      
    	exports.execute = function(req,res){
    		//just like express.router function
      		
    		//this will render the configured view
    		res.result("success",{data:""});
      		
    		//if something goes wrong , you can render the error view
    		res.result("error");
      		
    		//you can also call the any methods of  express.Response
    		res.send("welcome");
      		
    	}
      
  • Finish ! visit localhost:3000

For more details , run ./example/bin/www .

API

  • sledge(urlPattern , config , baseControllerPath);

    • urlPattern any pattern supported by express

    • config Object , see lib/config.json

    • baseControllerPath path of routers directory. require("path").join(__dirname , "routes")

    This will parse the config to express.Router and add function result to express.Response . You can use this function to choose which view to render. Of course , you can still use express.Response.render or other functions.