v<%= releaseVersion %>

v<%= releaseVersion %> adds more flexible shell transforms, easier HTTP management with automatic CORS preflighting and forms parsing, and a number of bug fixes.

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

New Features

The shellTransform behavior now accepts an array, allowing you to create a shell pipeline of transformations
Support for automatic stubbing of CORS preflight requests with the allowCORS flag on http/s imposters
New API call to delete saved proxy requests without changing the stub itself
New form request field for http/s that allows object predicates on form-encoded HTTP body data.
Added scripts to install mountebank as a system daemon

Bug Fixes

Fixed jsonpath deepEquals predicate on boolean values ( #280)
Fixed order of indexed jsonpath selectors in predicates ( #283)
Fixed nested template problem using the --configfile CLI parameter when an extra newline is added to the template ( #293)
A failed PUT command sent to /imposters no longer deletes all imposters (#246)
Fixed the exists predicate with integer values, null values, and object values (#299)

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

Amy Martin
Ruud Kamphuis
Karl Brown
Sahejpreet Singh
Mario Lamontagne

Install

npm install -g mountebank@<%= releaseVersion %>

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