v1.7.2
Bug Fixes
- Fixed a bug allowing state changes to the
"is" response after creation. This was first noticed when using the
decoratebehavior - the second and subsequent calls incorrectly returned whatever the first call used - Correctly show the number of requests on the imposters page
- Prevent using functions for the
waitbehavior unless the--allowInjectionflag is passed in. - Fixed some documentation, especially around the behaviors
Many thanks to the following kind folks for help with this release:
- nottyo
Install
npm install -g mountebank@1.7.2or:
| Option | node.js required? | sudo required? | links | Description |
|---|---|---|---|---|
| Self-contained archives | No | No | Simply unpack and run mb from inside |
|
| OS-specific packages | No | Yes | Puts mb at /usr/local/bin, which is generally in the PATH. |
|
| source tarball | Yes | No | 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
npmto install mountebank instead of the zip file