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-crud

v4.0.1

Published

Easy CRUD for express apps!

Downloads

58

Readme

express-crud NPM version Downloads Build Status Coveralls Status

Easily route a resource's crud methods to express apps!

##Example Here's a User resource that exposes some CRUD methods:

module.exports = {
  create:   function(query, model, cb){
  ....
  cb(null, ["create"]); //first argument is response status, second is array of response data
  },
  delete:   function(id, query, cb){},
  read:     function(query, cb){},
  readById: function(id, query, cb){},
  update:   function(id, query, model, cb){}
};

Here's how you add the routes to your express app:

var app = require('express')();
var User = require('./models/User');

require('express-crud')(app);

app.crud('users', User);

Here's how you add the routes to your express app using a formatted response object:

var app = require('express')();
var User = require('./models/User');
var opts = {
	formatResponse: function(result) {
		return {
			timestamp: Date.now(),
			payload: result
		};
	}
};

require('express-crud')(app, opts);

app.crud('users', User);

Now your express app has the following routes:

DELETE /users/:id
GET /users
GET /users/:id
POST /users
PUT /users/:id

Changing the param name

You can change the param name by specifying it at the end of your route:

app.crud('users/:userId', User);

Now your express app has the following routes:

DELETE /users/:userId
GET /users
GET /users/:userId
POST /users
PUT /users/:userId

###With some middleware

var authorizeMiddleware = function(req, res, next){//arity matters!
  if(req.query.username !== 'foo')return next(new Error('user not foo!'));
  next();
};
var fooMiddleware = function(req, res, next){next();};

app.crud('users', authorizeMiddleware, fooMiddleware, User);

Restrict access to resources by user

app.crud('settings/:settingId', authorizeMiddleware, function(req, res, next){
  //ensure that the resource get's the username.
  req.query.username = req.user.name;
  next();
}, SettingsResource);

Format your response

With any path

app.crud('/any/old/path/for/users', User);

Status Codes

When you call the callback given to resource methods without an error object as the first arg, express-crud will use either 204 or 200 depending on the context. If you wish to pass a non 2xx status code up to your application the preferred way is to assign a status property to your error object I.E. cb({status: 404}).