v1.9 adds some really nice features and fixes important bugs. Thanks for all the help getting it across the line.
- Added a new
lookupbehavior that allows you to add data in the response that comes from an external data source. Initially, a CSV file is the only data source supported.
- Added an ability to add a decorator to the newly created response saved through
proxyresponse type with the
- Support for stateful predicate injections based on response injections changing state.
imposterStateparameter has been added to each injection function.
- A few new FAQs based on common queries around npm shrinkwrap, CORS pre-flight requests, and preventing proxies from compressing data.
- The default self-signed certificate for https imposters is no longer expired
- Fixed content-length issues with binary data coming from proxied results
- Fixed a bug preventing you from seeing the _links field in your imposter body when getting the imposter state through the API
Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
- Stephen Tkac and team, for the suggestion and initial implementation of the
- Kevin Pouget for adding support to decorate saved responses from proxies
- Gabriel Kohen for adding support for stateful injections to use in predicates
- Adam Kalman for helping
npm install -g email@example.com
|Option||node.js required?||sudo required?||links||Description|
|Self-contained archives||No||No||Simply unpack and run
|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
npmto install mountebank instead of the zip file