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

@rippell/mock-server

v0.0.2

Published

Simple express server managing mocks for rapid development

Downloads

3

Readme

Mock Server

Super simple mock server that allows applications to be built as if hitting a real server because having to make code changes to run locally vs in production isn't cool.

Goals are to:

  • Keep code and mocks separated
    • No code changes for mocking and mocks aren't bundled with code
  • Keep mocks and data close to the code
    • Clean organization and not a jumbled mess of spaghetti files
  • Allow for extensible mocking of responses and statuses
    • Give open access to the underlying server without complications
  • Live-reload!
    • Keep up with fast paced development by refreshing mocks when files are changed

Install

Install as a dev dependency, along with npm-run-all to run in parrallel with your code development server.

npm i --save-dev @common/mock-server npm-run-all

Create a proxy configuration file at the top of the project to proxy all HTTP calls to the mock server (proxy.mock.json)

{
  "/api": {
    "target": "http://localhost:4300",
    "secure": false,
    "debug": true
  }
}

Change start command to start both servers:

{
    ...
    "start": "npm-run-all --parallel mock-server start-proxy-mocks",
    "start-proxy-mocks": "ng serve --proxy-config proxy.mock.json",
    "mock-server": "mock-server",
    ...
}

Basic Usage

When booting up, a file scan is done to discover controllers - *.mock.js files. It's recommended to keep the mock file with the service it belongs to. By default the Mock Server will search /src/ for all files matching *.mock.js to register with the server.

my-project
 |- node_modules
 |- src
     |- app
         |- services
             |- my-service
                 |- myService.service.ts
                 |- myService.mock.js
                 |- myService.data.json

myService.mock.js

module.exports = {
  '/api/v1/endpoint': {
    get: (req, res) => {
      res.json({ msg: 'Hurrah!'});
    }
  }
}

If mock data is large, it's also common to create a .json file and include it into the *.mock.js.

myService.data.json

{
    "mySubObject": {
        "msg": "Sweet response!"
    }
}

myService.mock.js

var data = require('./my-data.json');

module.exports = {
  '/api/v1/endpoint': {
    get: (req, res) => {
      res.json(data.mySubObject);
    }
  }
}