fidelman/mokker

The mock does not mock you. The video: https://www.youtube.com/watch?v=gGLNJpC-Ov0

Mokker

Mokker is a simple express RESTful API mock server, which also provides few methods to make your data emulating easier.

Installation

npm install --save-dev mokker
yarn add --dev mokker

Dependencies

• body-parser
• express
• morgan
• query-string
• react-dev-utils

Usage

// server.js
const mokker = require('mokker');

const routes = [{
    method: 'get',
    url: '/api',
    json: { is: 'done' }
}];

mokker.start({ routes });
// done 😍

$ node server.js

Docs

• API
• Examples

License

This project is licensed under MIT License. See the license file for more details.

mokker's Issues

Title/fileName in docs has been failed

it is failed when title/fileName contains slashes

Allow Access-Control-Allow-Headers by setting

@fidelman could you please add an option to set Access-Control-Allow-Headers from mokker.start or somewhere else?

Because I need another header x-on-behalf-of which you don't set in the start of the server and maybe there can be other headers later as well.

// hardcoded headers
res.header('Access-Control-Allow-Headers', 'Content-Type, Authorization, Content-Length, X-Requested-With, X-Redmine-API-Key');

Thanks!

Repository improvement

What

Sharing my thoughts and pieces of advice to improve this repository.

Why

Good repository - good library - good experience.

How

• index.js@31 consider the scenario when the port provided to mokker is already in use. Express knows how to fallback to another port, make sure to print out the fallback port in case this happens.
• routes.js@31 missing space. Right now it would produce: GETis (a) wrong method.
• Isn't request a save dependency?
• Export library in the supported format. Right now you are using arrow functions, which is a relatively new feature. This may cause your library to fail on old projects. Use bundle tools (webpack, rollup) to bundle the transformed library (see libraryTarget option in webpack and ES6 => ES2015).
• Introduce minification to the built bundle. The tools mentioned above will help.
• Do not use version 1.0.0 if it's not yet released (does not have stable API, etc.). A good place to start is 0.1.0. Make sure to read about Semantic versioning.

Add error hanlers