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

restify-express

v0.2.2

Published

Middleware to create REST APIs on express server

Downloads

4

Readme

restify-express Build Status Downloads npm version Dependency Status

Middleware to create REST APIs on express server

Installation

Works with Express 4.x.x

npm install restify-express

Usage

var express = require('express');
var rest = ('restify-express');
var router = express.Router();

var app = express();

app.use({
  controllers: __dirname + '/' + 'controllers',
  app: app,
  base: '/api',
  router: router,
  verbose: true
});

Next is to create controllers in your controllers folder. Let's create posts.js file with below sample code:

var Post = {
    __NAME : 'posts',
    index : function(req, res) {
        return res.json({'message' : 'This is index page'});
    },
    create : function(req, res) {
        return res.json({'message' : 'Create a new post'});
    },
    update : function(req, res) {
        return res.json({'message' : 'Update an existing post'});
    },
    read : function(req, res) {
        return res.json({'message' : 'read a post'});
    },
    destroy : function(req, res) {
        return res.json({'message' : 'Delete a post'});
    },
    custom: {
        method: 'get',
        params: '/:x/:y',
        handler: function(req, res) {
            return res.json(req.params);
        }
    }
}

module.exports = Post;

__NAME is required field. If it is not present then entire file will get ignored.

It will create following URLs:

  • GET /api/posts : Post.index
  • POST /api/posts : Post.create
  • PUT /api/posts : Post.update
  • DELETE /api/posts : Post.destroy
  • GET /api/posts/:id : Post.read
  • GET /api/posts/:x/:y : Post.custom

New in 0.0.5

  • We are moving towards convention over configuration. Now __NAME field has become optional in controllers. By default it will consider file name and it can be overridden using __NAME field.

  • we have added two more functions to response object to handle success and error responses:

    • res.successJson(json)
    return res.successJson({'message': 'This is success message'});
    
    above code will return below json with http status code 200:
    {
        status: "success",
        data: {
            message: "This is success message"
        }
    }
    • res.errorJson(json)
    return res.successJson({'message': 'This is error message'});
    
    above code will return below json with http status code 400:
    {
        status: "error",
        data: {
            message: "This is error message"
        }
    }