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

@ztang/mountebank-formatters

v0.0.4

Published

The default parsers and formatters for managing mountebank test data

Downloads

5

Readme

Formatters

As of v2.4.0, mountebank supports custom formatters.

A formatter consists of two functions:

  • load, which loads the --configfile used to start mountebank
  • save, which saves the test data captured in a running process of mountebank using the mb save command

Those two functions should work in concert, so you can round-trip the configuration. In other words, the following should always work for the same formatter:

mb save --savefile mb.json --formatter path/to/customFormatter
mb restart --configfile mb.json --formatter path/to/customFormatter

For years, mountebank supported EJS templating, which could be turned off using the --noParse CLI flag. When EJS made a breaking change, mountebank couldn't accept it because it would break existing config files. That has now been modularized into this module (allowing mountebank core to upgrade EJS), and remains the default option for backwards compatibility. However, now mountebank supports configurable formatters.