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

express-rest-builder

v1.0.1

Published

Simply build REST API with Express.js!

Downloads

3

Readme

Express REST Builder

Build REST API using Express.js with ease!

Introduction

This package was inspired by Laravel's resource controllers which simplifies creating REST services a lot. Same minimalistic approach was applied in this package to include only the most commonly used HTTP methods and abstract their logic from the developer. Write less to get more!

Example

index.js

var express = require("express")
var app = require("./express-rest-builder")(express())

app.listen(8080, function() {
    console.log("Listening on port 8080...")
})

app.restResource("posts", {
    getAll: (request, response) => response.json([{post: "here's a post yo"}, {post: "here's another post yo"}]).end(),
    getOne: (request, response) => response.json({post: "here's a post yo", id: request.params.posts}).end(),

    post: (request, response) => response.json({post: "saved that post yo"}).end(),
    put: (request, response) => response.json({post: "edited this post yo", id: request.params.posts}).end(),
    delete: (request, response) => response.json({post: "deleted this post yo", id: request.params.posts}).end()
})

app.restResource("posts.comments", {
    getAll: (request, response) => response.json([{comment: "here's a comment yo", post_id: request.params.posts}, {comment: "here's another comment yo", post_id: request.params.posts}]).end(),

    post: (request, response) => response.json({post: "commented on that post yo", post_id: request.params.posts}).end(),
    delete: (request, response) => response.json({post: "deleted this comment yo", id: request.params.comments}).end()
})

Installation

Two steps:

  1. npm i express-rest-builder
  2. Done.

API

Express REST Builder extends the app object of the Express.js. Therefore, to initialize it you have to require it and pass the app as a parameter:

var express = require("express")
var app = require("./express-rest-builder")(express())

Now you have a restResource function available on the app object.

app.restResource(resource, options)

resource string Required

The string describing the resource, will be parsed into a URL. For example, "posts" will become /posts/:posts route with optional parameter depending on the HTTP method. For nested resources separate them with a dot, so "posts.comments" will become /posts/:posts/comments/:comments route with :comments being an optional parameter depending on the method.

Note: route parameters always have the exact same name as the resource they're associated with.

options object Required

The object mapping the operations (HTTP methods) to the resolvers. All the available operations with the routes they create are described in the table below.

| Name | URL | Method | |:---------|:--------------|:-----------| | getAll | /posts | GET | | post | /posts | POST | | getOne | /posts/:posts | GET | | put | /posts/:posts | PUT | | delete | /posts/:posts | DELETE |

License

Apache License 2.0