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

@iyogeshjoshi/postman-mock-server

v0.1.1

Published

Provides the ability to run Postman collections as a local mock server.

Downloads

123

Readme

Postman Local Mock Server

npm version

This project brings Postman's collection mocking capability locally enabling you to create mock servers quickly and run tests against these.

Quick Start

npm install -g @iyogeshjoshi/postman-mock-server
postman-local -c path/to/collection.json -p 8080

Capabilities

  • Create a local mock server by supplying a Postman Collection.
  • Customizable TCP Port number for your mock server.
  • Supports the x-mock-response-name and x-mock-response-code headers to specify the response you want returned by either name or status code.
  • Supports the x-mock-match-request-body header to match responses on POST/PATCH/PUT requests.
  • Full support for Postman's dynamic variables in example responses.

Using in your project

  1. Run npm install @iyogeshjoshi/postman-mock-server
  2. Add the dependency to your project and start the server.
const PostmanLocalMockServer = require('@iyogeshjoshi/postman-mock-server');

//Create the collection object.
let collection = JSON.parse(fs.readFileSync('./test/test-collection.json', 'utf8'));

//Create a new server
let server = new PostmanLocalMockServer(3555, collection);

//Start the server
server.start();

//Run some requests against your server
axios.get(`http://localhost:3555`).then(res => {
  //do something with the mocked response.
});

//Stop the server
server.stop();
  1. The server will now have endpoints available that match your specified collection.

Known Issues/Limitations

Tests/Prerequest scripts are not executed

This emulates the endpoints of a collection and the associated example responses. It does not invoke the pre-request or test scripts within a request.

As such, any requests that are reliant on variables (either collection/environment or global) will not work in this library.

Responses for the same path will take the first available

If your collection has the same path (e.g. /api/products) available multiple times, the first response defined will be the one returned by default - regardless of whether this is a successful or error response code.

There are several ways to overcome this:

  • Use the x-mock-response-name header on your requests to name the mock response you want returned.
  • Use the x-mock-response-code header on your requests to specify the response code (e.g. 200, 404) you want returned.

If you still cannot get the server to return your specific response, create an issue on this repo with the collection supplied and we'll try to replicate.

Request Matching algorithm differs from official Postman algorithm

  • This library uses a simple scoring based algorithm that does not fully match the more complex official algorithm
  • Notable differences include:
    • Requests with a trailing slash will not be matched at all
    • Requests with different casing will not be matched at all
    • Logic to match requests with query parameters and their values differ in the exact scores returned
    • No document distance / wild card / partial URL matching is supported

HTTPS is not supported

  • server only exposes HTTP endpoints (but it is localhost only)

Contributions

Contributions are welcome on this repo. Submit issues or PRs and these will be reviewed for merging.

License

See the LICENSE file.