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

parrot-mocker-web

v1.5.4

Published

Retransmit requests to real servers or just mock

Downloads

10

Readme

parrot-mocker-web npm version Build Status Coverage Status License

中文文档

This project provides a simple mock server, which works with the Chrome plugin parrot-mocker.

Support:

  • foward requests of pages(xhr/jsonp/fetch) to the real web server, or just mock
  • list all forwarded requests
  • config mock rules for different requests

Not support:

  • cookie sensitive requests, because the plugin forwards requests with cookies of the page, instead of cookies of the request domain
  • relative or local DNS parsed requests, because the mock server can not resolve them
  • ~~HTTPS pages, unless the mock server is deployed with HTTPS~~ (Solved by leancloud and now.sh)

How to use

1.Prepare

Install Chrome plugin, parrot-mocker, so that your pages have the ablity to intercept requests and forward to this mock server. Other usages without the plugin can refer to parrot-mocker project.

2.Visit

For example, if deployed in leancloud, please open your Chrome browser and visit index page first. Other instances like now.sh are similar.

Then visit your test page, i.e. my demo, which will send 3 different requests(xhr/jsonp/fetch) after loaded.

In the plugin, input the mock server address and click the green button. The test page will reload automatically.

Now you will find that requests are forwarded to the mock server, which are also visiable at index page. If visiting other pages in the same domain, their requests will also be forwarded to this mock server.

3.Mock

Click any request in the list, and click 'Add'. Then this request is added to mock.

Open config page, now you can edit the mock data. Remember to click 'Apply' to really use the mock data.

Refresh your test page to check whether the mock is working correctly.

Launch locally

By default, the server is launched on main port 8080, and sub-ports 8442/8443. Sub-ports can be visited by http/https correspondingly. Because my https is self-certified, if your browser gives a warning, please continue to visit.

node ./server/index.js

Or you can specify the port by an environment variable.

PORT=8888 HTTP_PORT=9442 HTTPS_PORT=9443 node ./server/index.js

Local index page is http://127.0.0.1:8080. You should use this address as mock server in step 2, and other steps are similar with above.

License

MIT

Acknowledgement