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 🙏

© 2025 – Pkg Stats / Ryan Hefner

em-rest-service

v0.2.0

Published

RESTful Service Middleware for ee-webservice

Readme

em-rest-service

RESTful Service Middleware for ee-webservice

installation

npm install em-rest-service

build status

Build Status

usage

You need to create controllers for each collection and each resource you plan to make available via the service. a collection is a collection of resources ( «/user» ), a resource is a single resource of a collection ( «/user/3» ).

URLs must be formatted as «collection/id» pairs so that they can parsed by the service

bad

  • user/comment
  • user
  • user/4/comment/images

good

  • /user/4/comment
  • /user
  • /user/4/comment/6/image

See the Joinbox RESTFul Style Guide for more information.

controller

var   Class 		= require('ee-class');

module.exports = new Class({

	// handles the get request on the collection
	get: function(request, response, next) {
		log( request.resource ) // the id of the resource
		log( request.mapping ) // a tree of colelctions which
							   // describe the mapping this resource resides on

		if (request.mapping){
			// the url called was /user/:id/comment/:id 
			// this could be another mapping if there are multiple mappings
			// for the comments collection / resource
			response.render( 200, [] );
		}
		else {
			// the resource was called on the root /comment/:id
			response.render( 200, [] );
		}

		// if this were a resource controller there would be a «resource»
		// property on the request. it would conatin the id / unique key
		// of the requested resource. log(request.resource) // 32432
	}
});

service

var   RESTService 		= require('em-rest-service')
	, Class 			= require('ee-class')
	, CommentCollection = require('CollectionController');


module.exports = new Class({
	inherits: RESTService


	, init: function init() {
		// you may load controllers from a direcotry or do the work yourself
		var commentsCollectionController = new CommentCollection();

		this.use('/user/:id/comment', commentsCollectionController);
		this.use('/comment', commentsCollectionController);

		// load controllers from a diretoy
		var options = {};
		options.controller = './controllers';
		options.controllerOptions = { anything: 'that', should: { be: 'passed' }, to: { the: 'controlers' } };

		init.parent(options);
	}
});

test.js / application

var   MyService		= require('MyService')
	, WebService 	= require('ee-webservice');

// start the webservice
var service = new WebService({
	port: 80
});

// create an instance of my service implementation
var myService = new MyService();
myService.on('load', function(){
	service.listen();
});

// add myservice middleware to the webservice
service.use(myService);