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

@ris/mock

v1.0.1

Published

ris mock middleware.

Downloads

13

Readme

@ris/mock

npm version npm downloads

A light-weight mock tools for webpack server or standard express server.

Getting Started

npm install @ris/mock --save-dev

In the webpack.config.js, we inject @ris/mock as a middleware in the after option.

const mock = require('@ris/mock');

module.exports = {
  //...
  devServer: {
    compress: true,
    port: 9000,
    after: (app) => {
      // Start mock data
      mock(app);
    },
  }
};

In our project root folder, we create mock folder and mock/rules.js file.

mock/rules.js will like this:


module.exports = {
  'GET /api/user': { name: 'beyondxgb' },
  'POST /api/form/create': { success: true },
  'GET /api/cases/list': (req, res) => { res.end(JSON.stringify([{ id: 1, name: 'demo' }])); },
  'GET /api/user/list': 'user/list.json',
  'GET /api/user/create': 'user/create.js',
};

When then browser send a request, for example, GET /api/user, if the rules you config in the mock/rules.js is matched, then it will directly response the data you config.

In the above rules, when browser send a request GET /api/user, then the server will response { name: 'beyondxgb' } to the client.

Config

mock/rules.js return a plain object. In the object, it is a key/value format.

module.exports = {
  'GET /api/user': { name: 'beyondxgb' },
};
  • key: it will like [method] [api]

  • value: it can be string/object/function/file

    • string/object:

    Directly config the response data.

    module.exports = {
      'GET /api/user': 'beyondxgb',
      'GET /api/user': { name: 'beyondxgb' },
    }
    • function:

    You can control the response data flexibility through req/res.

    module.exports = {
      'GET /api/user':  (req, res) => { res.end('beyondxgb'); }
    }
    • file:

    You can split the response data to file, only support .js and .json.

    module.exports = {
      'GET /api/user':  'user/info.json'
      'GET /api/user/create':  'user/create.js'
    }

    Then you should create file mock/user/info.json and mock/user/create.js:

    mock/user/info.json:

    {
      "name": "beyondxgb"
    }

    mock/user/create.js:

    module.exports = (req, res) => {
      res.end('ok');
    };