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

web-mock-server

v2.2.2

Published

Mock-server is a Node.js web site for mock data,and switch between mock data and real data.一个WEB版的数据模拟及文档管理系统

Downloads

5

Readme

Mock-server is a Node.js web system for mock data,and switch between mock data and real data.

中文文档

Features

  • Supports jsonEditor

  • Supports method types: GET、POST、PUT、DELETE...

  • RESTful path format,e.g: /a/:user/:id

  • Allow to specify status code,default:200

  • Supports delay to return data

  • Supports Mockjs

  • Supports json for cross-domain calls

  • Supports switch between mock data and real data

  • Supports switch between Chinese and English

  • Support 'text/plain' type post

demo

This demo is for demonstration purposes only.The System will clear data regularly

Install dependencies

npm install

Initialize database

  1. Use MockServer automatic initialization feature (recommend)
  2. Manually import .sql file
mysql[5.7.14]+,
import mysql file [mockserver-xx-xx.sql]
mysql coifnig in [/src/common/config/db.js]

Config

/src/common/config/config.js

Start server

npm start
#Server running at http://127.0.0.1:8033/

Examples

Suppose:

  • Mock Server running at http://127.0.0.1:8033
  • Created a API : /api/demo

cross-domain:

With the jQuery AJAX methods:

    $.getJSON('http://127.0.0.1:8033/api/demo').done(function(){
    
    
    }).fail(function(){
    
    })

Same domain and mock-server proxy URL different with nginx server_name:

Suppose:

  • Mock Server running at http://127.0.0.1:8033
  • Created a API : /api/demo

nginx config:

        server {
            listen 80;
            server_name your.site.com;
            root your/project/path;
    
            gzip_static on;
    
            # proxy to mock server
            location ^~ /api {
                proxy_pass http://127.0.0.1:8033;
            }
           
    
            # Attempt to load static files, if not found route to @rootfiles
            location ~ (.+)\.(html|json|txt|js|css|jpg|jpeg|gif|png|svg|ico|eot|otf|woff|woff2|ttf)$ {
                add_header Access-Control-Allow-Origin *;
    
                try_files $uri @rootfiles;
            }
    
            # Check for app route "directories" in the request uri and strip "directories"
            # from request, loading paths relative to root.
            location @rootfiles {
                rewrite ^/(?:foo/bar/baz|foo/bar|foo|tacos)/(.*) /$1 redirect;
            }
        }

Same domain and mock-server proxy URL equals nginx server_name:

Suppose:

  • Your Web Server running at http://127.0.0.1:8034
  • Mock Server running at http://127.0.0.1:8033
  • Created a API : /api/demo
  • Proxy URL value : http://www.site.com
  • Nginx server_name : www.site.com

nginx config:

        server {
                   listen 80;
                   server_name  www.site.com;
                   root your/project/path;
                   gzip_static on;
                    
                   location ^~ /api {
                       set $is_proxy 0;
                       # $http_is_mock_server_proxy comes from mock-server when mock-server's proxy is opened
                       if ($http_is_mock_server_proxy){
                           # $http_is_mock_server_proxy is mock-server writed header
                           set $is_proxy $http_is_mock_server_proxy;
               
                       }
                       # $is_proxy
                       # nginx proxy to mock-server
                       if ($is_proxy = 0 ){
                           proxy_pass http://127.0.0.1:8033;
                           break;
                       }
               
                       #Avoid circular proxy
                       if ($is_proxy = 1 ){
                           add_header http_is_mock_server_proxy "$my_header";
                           proxy_pass http://127.0.0.1:8034;
                           break;
               
                       }
                   }
                   location  / {
                       proxy_pass http://127.0.0.1:8034;
                   }
               
               }

Ajax in your.site.com:

    $.getJSON('/api/demo').done(function(){
    
    
    }).fail(function(){
    
    })