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

v0.3.1

Published

Build restful routed applications.

Downloads

40

Readme

express-resource-architect

Kickstart applications with resources

Build Status

This currently is in heavy development. It might quickly change. You should probably not use it before 1.0.0.

Idea

As we're developing many applications in a restful manner with express and mongoose, I saw a lot of code being duplicated over and over again. We've got many use-cases where a resource should be manageable using a nice interface. In 80 percent of all cases, this consists of the typical MVC views:

  • new
  • create
  • edit
  • update

We solve this by splitting such a resource in 2 parts. One is the route registration, the second is the controller which is representated using the route-handler an express app receives.

Example:

Route registration

express = require('express')

controllers = require('./controllers/users')

app = express()

app.get '/users/new', controllers.new

Controller (controllers/users.coffee)

mongoose = require('mongoose')

User = mongoose.model('User')

exports.new = (req, res, done) ->
  user = new User()
  res.render 'users/new', user: user

Controllers of those simple cases are needed over and over again. This is really error-prone and could be abstracted I think so I started this tiny module.

The first abstraction is the idea that controllers should have simple default routes based on their name. So using this module we could write the above example like the following:

architect = require('express-resource-architect')
mongoose = require('mongoose')

resource = architect(app)

resource mongoose.model('User'), require('./controllers/users')

The controller is then as easy as this:

architect = require('express-resource-architect')

c = architect.controllers()

exports.new = c.new()

This is a really leaky abstraction you may say, but for cases where you need more control we also got some awesomeness: middleware. These are tinier pieces of a controller (in fact every controller consists of middleware) which can be used independly. This does the same as the above example:

architect = require('express-resource-architect')

m = architect.middleware()

exports.new = [
  m.new()
  m.view 'users/new', true
]

I'm currently working hard to shape the API and stabilize this thing. Currently it's an idea that follows frameworks like sails or ruby on rails but without the bloat and the loss of flexibility since it always remains express.