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

imock-tool

v0.3.1

Published

Mock Backend Server

Downloads

5

Readme

imock

Mock Backend Server

Quick Start

Install Module globally

$ npm install -g imock-tool

Intital Project

$ mkdir job && cd job
$ imock init

or

$ imock init job

Start Up Server

$ imock 

Use As A NodeModule?

var imock = require('imock-tool')
var app = imock({
	
},callback)

callback

Allow custom callback function after express server listened, default callback will be used if callback is not specified.

Routes

Routes is stored in route.js as key/value pairs by default.

Sample:

module.exports = {
    // set json api with a json/js file in mock folder
    'POST::/test':         'mock::test.js',

    //simple proxy
    'GET::/api'  :         'https://domain.com/api'
}

the rule is '[method]::[route_url]': '[template_file]'.

Allowed method: GET, POST, PUT, PATCH, DETELE

GET will be used if it is not specified.

Response Body

module.exports = {
	'$$statusCode':404,
	'$$delay':3000,
	'$$header':{
		'Content-Type':'application/json'
	},
	'message':'hello world'
}

$$statusCode

deafult: 200

The http response status

$$delay

default: 0

The http response delay

$$header

The http response header

Configuration

basePath

The base path of the project, all other folder settings are related to base path.

mockFolder

default: 'mocks'

Save you mock data into this folder.

routeFile

default: 'route.js'

Routes mapping file

port

default: 3000

Express server port

proxy

deafult: null

How to use proxy ?

middlewares

default: null

livereload

default: true

livereload is awesome, it will restart your server automatically after anything of mockFolder changed.