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

connect-mock-rest

v1.3.0

Published

Connect middleware to mock rest endpoints with json files

Downloads

2

Readme

connect-mock-rest

Mock rest API middleware for connect. It turns any json file in to a rest API.

When using this middleware GET, POST, PUT, PATCH and DELETE can be performed on any json file. This is useful for rapidly prototyping an application using only json files as endpoints.

This module works particularly nice when combined with my fork of TJ's serve which can be found here.

Setup

$ npm install body-parser
$ npm install connect-mock-rest

Usage

var path = require('path')
  , connect = require('connect')
  , mockRest = require('connect-mock-rest')
  , bodyParser = require('body-parser');

var server = connect();

server.use(bodyParser());
server.use(mockRest());

If you are serving from a different location you need to specify that:

server.use(mockRest(path.join(__dirname, 'public')));

Create a json file containing an array. In this example /foo.json contains []. Start your server and then:

$ curl http://localhost:3000/foo.json
[]

$ curl -H "Content-Type: application/json" -X POST -d '{"name":"steve"}' http://localhost:3000/foo.json
{"name":"steve","id":"29b6ae06-87ec-422c-9efc-ad3c7e759364"}

$ curl http://localhost:3000/foo.json
[{"name":"steve","id":"29b6ae06-87ec-422c-9efc-ad3c7e759364"}]

$ curl -H "Content-Type: application/json" -X PUT -d '{"name":"foo"}' http://localhost:3000/foo.json/29b6ae06-87ec-422c-9efc-ad3c7e759364
{"name":"foo","id":"29b6ae06-87ec-422c-9efc-ad3c7e759364"}

$ curl http://localhost:3000/foo.json
[{"name":"foo","id":"29b6ae06-87ec-422c-9efc-ad3c7e759364"}]

$ curl -H "Content-Type: application/json" -X PATCH -d '{"name":"bar"}' http://localhost:3000/foo.json/29b6ae06-87ec-422c-9efc-ad3c7e759364
{"name":"bar","id":"29b6ae06-87ec-422c-9efc-ad3c7e759364"}

$ curl http://localhost:3000/foo.json
[{"name":"bar","id":"29b6ae06-87ec-422c-9efc-ad3c7e759364"}]

$ curl http://localhost:3000/foo.json/29b6ae06-87ec-422c-9efc-ad3c7e759364
{"name":"bar","id":"29b6ae06-87ec-422c-9efc-ad3c7e759364"}

$ curl -X DELETE http://localhost:3000/foo.json/29b6ae06-87ec-422c-9efc-ad3c7e759364
{"name":"bar","id":"29b6ae06-87ec-422c-9efc-ad3c7e759364"}

$ curl http://localhost:3000/foo.json
[]

Things to note

  • This is intended for rapid prototyping purposes only. You would be mad to use this on any real project.
  • Objects are created with a GUID which is stored as id. Any existing id will be overwritten.
  • Resource nesting is not supported.
  • Security is not considered at all.
  • Invalid requests will not be handled well. This thing is far from bulletproof.
  • There is no validation of incoming data.
  • Duplicate objects will be created if the same object is posted twice.
  • When finding items the first match is returned. This applies to all methods.