v2.3.0

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

The focus of this release is revamping the behaviors pipeline to put more control into the hands of the users. See the behaviors page for the new syntax, which allows complete control over the behaviors pipeline. The one previous behavior that doesn't compose into a pipeline of post-processing transformations is repeat, which is now treated as a response parameter.

As always, despite being a syntactically breaking change, there are strong backwards compatibility enforcements. There is no need for you to upgrade your scripts to the new syntax; mountebank will continue respecting the old syntax without change.

New Features

Changed the behaviors pipeline into a composable pipeline with the user in complete control of the order of operations. Previously, some behaviors (like copy and shellTransform) took arrays, which meant that some behaviors supported a pipeline and some didn't, and there was no way to control the order of operations, meaning you were unable to reason deterministically about what would happen if you had both a shellTransform and decorate behavior. To make this work, the repeat behavior has been changed to a response parameter.
Allow the decorate behavior access to the imposter's state variable
Added a new community UI to the options for manual use.

Bug Fixes

Thanks to Robert Cooper, a fair amount of work was done to resolve intermittent file locking issues using the --datadir parameter.
Clarified docs on creating a custom protocol
Allow --protofile to use relative and absolute paths if included directly in JavaScript (rather than called through the CLI)

Contributors

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

Robert Cooper
cbrz

Install

npm install -g mountebank@2.3.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