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

mimicio

v1.0.1

Published

A simple CLI tool for running a mock API server based on a directory structure.

Downloads

13

Readme

mimicio NPM Libraries.io dependency status for latest release GitHub commit activity GitHub repo size npm

Mimicio

A simple CLI tool for running a mock API server based on a directory structure.

Installation

npm install -g mimicio

Directory Structure

The mock server uses a specific directory structure to determine the available services, methods, endpoints, and responses. Here's an example of how to set up your directories and files:

root
├── serviceName
│   ├── GET
│   │   ├── endpointName
│   │   │   ├── 200.json
│   │   │   └── 404.json
│   ├── POST
│   │   ├── endpointName
│   │   │   └── 200.json

In this example:

  • serviceName is the name of the service.
  • GET and POST are HTTP methods.
  • endpointName is the name of the endpoint.
  • 200.json and 404.json are JSON files representing the response bodies for their respective status codes.

Usage

Navigate to the root directory containing your service directories, then run the mimicio command:

mimicio

The mock server will start on a random available port in the range 3000-3999. The console will display the port number.

You can then send HTTP requests to the server. For example, if the server is running on port 3000, you could send a GET request to the endpointName endpoint of the serviceName service like this:

curl http://localhost:3000/serviceName/endpointName

The server will respond with the contents of the 200.json file in the GET/endpointName directory of the serviceName service. If the 200.json file does not exist, the server will respond with a 500 Internal Server Error.

License

This project is licensed under the MIT License.