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

v0.1.1

Published

Simple and semantic restful resource routing for Express

Downloads

5

Readme

Express Resource Router

Simple and semantic restful resource routing for Express

Installation

npm install --save express-resource-router

Usage

The API is simple - when you require the module, you will be returned the express.Router() function with eight new methods appended:

  1. resource - allows for autoloading of the resource being described
  2. index - sets up a '/' get route
  3. new - sets up a '/new' get route
  4. create - sets up a '/' post route
  5. show - sets up a '/:id' get route
  6. edit - sets up a '/:id/edit' get route
  7. update - sets up a '/:id' put route
  8. destroy - sets up a '/:id' delete route
// lets assume this is routes/posts.js
var router = require('express-resource-router');

router.resource(function(id, setResource) {
	// the third argument is optional - it sets req.post 
	// in this case, but req.resource is the default
	setResource(null, Post.find(id), 'post'); 
});

router.index(function(req, res) {
	res.render('posts/index', { posts: Post.all() });
});

router.new(function(req, res) {
	res.render('posts/new', { post: new Post() });
});

router.create(function(req, res) {
	var post = Post.create(/* post params */);
	res.redirect(linkTo(post));
});

router.show(function(req, res) {
	// without the third parameter above in router.resource(...), 
	// we would use req.resource
	res.render('posts/show', { post: req.post });
});

router.edit(function(req, res) {
	res.render('posts/edit', { post: req.post });
});

router.update(function(req, res) {
 	req.post.update(/* post params */);
	res.redirect('back');
});

router.destroy(function(req, res) {
	req.post.delete();
	res.redirect('/posts');
});

module.exports = router;

Then in your application file...

var app = require('express')();

app.use('/posts', require('./routes/posts'));

And you're good to go.

Contribution

Right now, I need to write tests for this. If you want to, have at it. Fork and PR, baby.