v2.4.0

Be sure to keep up with the latest releases by subscribing to the ATOM feed.

This release adds a significant amount of startup customization to mountebank.

New Features

Support for custom formatters when loading mountebank using the configfile CLI option or when saving test data using mb save. See the new formatter CLI option for details.
Allow passing a custom data object to stringify functions in the default EJS formatter for the configfile CLI option
Support gzip request content encodings, so predicates work on compressed requests.
Allow customizing the logging format with the log command line parameter.
Added the rcfile command line parameter, allowing you to keep startup configuration in a JSON file.
Added Prometheus metrics to help troubleshoot bottlenecks.
Reduced the Docker image size
Moved the 'No predicate match' message from the debug logs to the info logs to help troubleshooting when mountebank is generating a default response.

Bug Fixes

Correctly show the imposter name on the imposters page.
Fixed bug passing large requests or responses to the shellTransform behavior on Windows.
Allow copy behavior to replace JSON keys as well as data.

Contributors

Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:

Craig Harris
dcRUSTy
Colin Newell
Kishan B

Install

npm install -g mountebank@2.4.0

or:

Option	node.js required?	sudo required?	links	Description
Self-contained archives	No	No	osx linux x86 linux x64 win x86^* win x64^*	Simply unpack and run `mb` from inside
OS-specific packages	No	Yes	pkg rpm deb	Puts `mb` at `/usr/local/bin`, which is generally in the `PATH`.
source tarball	Yes	No	mb	source tarball if you roll that way.

Windows path limitations

^*mountebank wishes very much for your Windows experience to be hassle-free, but he is simply not qualified to address a particular constraint of Windows Explorer. For legacy reasons, some Windows applications, including most notably Windows Explorer, have a maximum number of characters allowed in a path of 260 characters. As mountebank writes these words, the longest path he includes in the zip files is around 175 characters. The zip file name, which is likely to represent itself as two nested directories if you use the defaults to unzip it, will be around 25 characters. That gives you very little wiggle room. If you unzip the file in your users directory, you may very likely get an error because of this constraint.

The following solutions will all work:

Unzip to the root of your C: drive (or a similar small path)
Use 7zip to unzip the file instead of Windows Explorer
Use npm to install mountebank instead of the zip file