Softpedia >Windows >Internet >Servers >Other Servers >Mockoon >  Changelog

Mockoon Changelog

What's new in Mockoon 8.1.1

Apr 30, 2024
  • Patch 8.1.1 fixes the following issues:
  • Since allowing opening multiple environments at once in v8.1.0, two bugs were fixed:
  • Files couldn't be opened anymore on macOS. (Issue #1379)
  • The same environment file could be opened multiple times. (Issue #1381)

New in Mockoon 8.1.0 (Apr 30, 2024)

  • Logs view improvements:
  • For this release, the desktop application's Logs view has been improved. It now includes a search bar to filter logs by URL, method, status code, query, or timestamp.
  • (Issue #1109):
  • We also added proper code editors for the request and response bodies in the logs view. They will now display the content with proper formatting and syntax highlighting, and show eventual errors for the JSON format. As a side effect, the bodies are now searchable:
  • (Issues #368 and #137):
  • Last modification, the "Last log" link displayed under the response body now shows when the request or response JSON was malformed
  • Admin API:
  • Since the introduction of the admin API in the previous release, we added multiple new features:
  • The admin API can now be deactivated when running your mock with the CLI or the serverless library. (Issue #1371)
  • You can now reset and update the global variables using the /mockoon-admin/global-vars endpoint. (Issue #1354)
  • The environment variables can be updated using the /mockoon-admin/env-vars endpoint. (Issue #1372)
  • The transaction logs of a running mock server can be fetched using the /mockoon-admin/logs endpoint. (Issue #632)
  • The data buckets can be regenerated without having to reset the full server state using the /mockoon-admin/data-buckets endpoint. (Issue #1373)
  • Head to the documentation to learn more about the admin API.
  • New CLI flags and serverless options:
  • We added new flags to the CLI to allow you to:
  • --disable-admin-api to deactivate the admin API. (Issue #1371)
  • --disable-tls to override the TLS settings and disable it when running in your CI server. (Issue #668)
  • --max-transaction-logs to set the number of logs kept in memory for retrieval via the admin API. (Issue #632)
  • Similar options have been added to the serverless library.
  • TLS and environment variables:
  • Templating is now supported in the TLS configuration, allowing you to use environment variables in the certificate paths and password fields.
  • Improvements:
  • You can now open multiple environments at once in the desktop application
  • Fixes:
  • The PATCH method wasn't working in the callbacks. This is now fixed. (Issue #1364)
  • Fixed a bug were the application could reconnect to the sync server with a previous token after switching to a different account. (Issue #1369)
  • Chores:
  • We updated the libraries and applications dependencies to their latest versions to fix some reported vulnerabilities.

New in Mockoon 8.0.0 (Apr 19, 2024)

  • Fixes:
  • We moved the execution of the callbacks after the response template generation to allow the callback's own templates to access the global variables. (Issue #1300)
  • The {{ipv4}} helper is now correctly returning only IPv4 addresses instead of a mix of IPv4 and IPv6. (Issue #1332)
  • Chores:
  • We updated the libraries and applications dependencies to their latest versions to fix some reported vulnerabilities.

New in Mockoon 7.0.0 (Mar 8, 2024)

  • We introduced some breaking changes in this major release:
  • macOS 10.13 and 10.14 support has been removed.
  • We disabled the JSONPath array "wrapping" feature.

New in Mockoon 6.1.0 (Jan 3, 2024)

  • CRUD filtering and searching:
  • This new feature adds search and filter options to the main GET endpoint of a CRUD route, using query parameters. Many operators are available to filter your data like _eq,_gt,_lte, or _start. They can filter on any property of the data, including nested properties using the dot notation:
  • /users?name_eq=John&age_gt=18&address.city_start=New
  • You can also use the search parameter to search for a string in all properties of the data:
  • /users?search=john
  • Global variables:
  • Mockoon now supports global variables that can be set and accessed using the setGlobalVar and getGlobalVar helpers at runtime.
  • {{setGlobalVar 'myVar' 'myValue'}}
  • {{getGlobalVar 'myVar'}}
  • These variables can be used anywhere templating is supported, like the response body or headers. Their values are reset when the environment is stopped or restarted.
  • OpenAPI import improvements:
  • The OpenAPI v3 specification server.url is now correctly parsed when it only contains a path (no protocol or domain). (Issue #1221)
  • The CLI is now correctly reporting the OpenAPI import errors alongside Mockoon's format parser errors. (Issue #1229)
  • Files with .yml extensions are now selectable in the OpenAPI import dialog. (Issue #1229)
  • CLI and Serverless new Faker.js options:
  • New flags were added to the CLI, and new options to the Serverless package, to allow setting the Faker.js locale and seed.
  • For the CLI, use the --faker-locale and --faker-seed flags. More information in the CLI's documentation.
  • For the Serverless package, use the fakerOptions.locale and fakerOptions.seed options
  • Desktop application:
  • Fix the data bucket name not being displayed on a CRUD route view when creating from the template modal. (Issue #1234)
  • Fix the Faker.js locale not being applied from the settings on startup. (Issue #1222)
  • Fix callbacks not being removed from the route response's callbacks view when deleted, in the case multiple responses were present. (Issue #1215)

New in Mockoon 6.0.1 (Dec 3, 2023)

  • Fixed a silent crash occuring when focusing a route in a folder of a new environment. (Issue #1210)
  • Fixed a null pointer exception when opening the command palette when no environment is open.
  • Some minor UI fixes.

New in Mockoon 5.1.0 (Nov 2, 2023)

  • New command palette:
  • We added a new command palette in the desktop application to quickly access all the application's features. You can open it by pressing Ctrl+P (Windows/Linux) or Cmd+P (MacOS). You can also access it by clicking on the icon in the header (see capture below).
  • It currently supports most common actions like creating new environments, starting/stopping them, opening the settings, etc. You can also search for any environment, route, or data bucket by typing their name or path. We will add more actions in the future. Let us know what you think, and do not hesitate to suggest new actions on our Discord server or GitHub discussions.
  • Faker.js v8 migration (potentially breaking):
  • Mockoon now uses Faker.js v8. This update packs a lot of changes regarding the helper names. Some were removed, and many were renamed. For example, name.firstName moved to person.firstName. Some new locales were also added, like Danish. Be sure to check their migration guide to learn more.
  • This new version (both desktop and CLI) will automatically update your environment's inline bodies and data buckets content. However, it won't migrate external files (JSON, CSV, etc.) containing templating helpers, and you will have to do it manually.
  • All the documentation and mock samples were updated to reflect these changes and avoid any confusion with old helpers names.
  • Range header support:
  • Mockoon now supports the Range header. This header is used to request only a part of a resource, like a binary file, to allow the download in chunks. You can now use it in your routes to simulate this behavior.
  • Head over to the documentation to learn more about this header.
  • Desktop application:
  • We fixed a bug occurring at startup when the application was maximized causing the environments and routes menus sizes to not be correctly restored from the settings and often reduced in size. We also fixed a rare bug caused by the same resizing feature that could propagate an erroneous state of the settings and result in an empty UI at startup. (Issue #1167)
  • We fixed a bug where the data bucket dropdowns would overflow the screen when displaying long names.
  • The log in modal is now automatically closed when the authentication happens through the custom protocol. (Issue #1158)
  • CLI:
  • We improved the error reporting during OpenAPI/data file parsing. (Issue #1161)

New in Mockoon 5.0.0 (Oct 3, 2023)

  • Breaking changes#:
  • We introduced two breaking changes in this major release:
  • We dropped support for Node.js v16. The CLI and the serverless package now require at least Node.js 18.
  • Support was dropped for legacy data files in both Desktop and CLI. If you are updating from v1.15.0, please first update to any version between v1.16.0 and v4.1.0, then to v5.0.0.
  • JSONPath support:
  • Mockoon now supports JSONPath alongside object-path everywhere a path to an object property can be provided:
  • in templating helpers like data, dataRaw, body, bodyRaw, queryParam and queryParamRaw.
  • in the response rules path.
  • We are using the JSONPath Plus library. Please refer to its documentation to learn more about the syntax. The simpler object-path syntax is still supported.
  • Routes targeting all HTTP methods:
  • It is now possible to create routes that will match any HTTP method. You can now select "All methods" in the routes method dropdown:
  • Global routes with rules:
  • Thanks to the response fallback mode introduced in v4.1.0, it was already possible to create wildcard routes containing "global" rules, like validating the presence of an Authorization header, or verifying that the request body contains a specific property. The only missing piece was the ability to create a global route that would match any HTTP method, which is now possible with the new feature above.
  • Head over to our new "Global routes with rules" documentation section to learn how to create reusable responses and rules and apply them to all your routes.
  • We also updated the desktop application's demo environment to showcase this new feature.
  • Desktop application#:
  • Breaking change: Support was dropped for legacy data files (pre v1.16.0). The desktop application will no longer automatically migrate your environments from the old system. If you are updating from v1.15.0, please first update to any version between v1.16.0 and v4.1.0, then to v5.0.0. (Issue #1138)
  • We added a link in the footer update notification to let you easily check the new version's changelog (will be visible for updates >v5.0.0):
  • CLI#:
  • Breaking change: We dropped support for Node.js v16. The CLI now requires Node.js 18 at least. (Issue #1119)
  • Breaking change: Support was dropped for opening legacy data files (pre v1.16.0). (Issue #1138)
  • The Docker image is now tagged with its major version. Starting with version 5, all v5.x.x will be tagged 5 and so on. (Issue #1132)
  • Serverless package:
  • Breaking change: We dropped support for Node.js v16. The package is now requiring Node.js 18 at least. (Issue #1119)
  • Chores:
  • We updated most of the application dependencies to their latest version in order to fix recent security vulnerabilities.

New in Mockoon 4.1.0 (Aug 31, 2023)

  • New response fallback mode:
  • A new response mode has been added. It allows you to fallback to the next route and ultimately the proxied server when no response rules match instead of serving the default response. Visit the documentation to learn more. (Issues #363)
  • Dynamic rules with templating:
  • The templating helpers are now supported in the rule values letting you create dynamic rules. (Issue #988)
  • Changes to templating helpers:
  • Two new templating helpers have been added to allow array filtering and object creation. (Issues #1103)
  • Properties with dots are now supported in the queryParam and queryParamRaw templating helpers. Escape the dots when you want to reach values contained in a property with dots. See the examples in our documentation. (Issue #1115)
  • The eq templating helper is now compatible with strings. (Issue #1114)
  • | Other changes:
  • Templating helpers in Handlebars files with .hbs or .handlebars are now correctly parsed. (Issue #1120)

New in Mockoon 4.0.0 (Jul 24, 2023)

  • We introduced two breaking changes in this major release:
  • The logs format changed to be standardized across all Mockoon applications and packages. See the logs standardization section below for more details.
  • The CLI was refactored to remove the PM2 dependency. See the CLI section below for more details.
  • Logs standardization and credentials filtering:
  • Logging has been standardized across all Mockoon applications and packages. This means that the logs will now be formatted the same way in the desktop application log file, the CLI's console and log file, and the serverless package's console logging. This will make it easier to read and parse the logs. As part of this change, we also added a new setting to enable full transaction logging to both the desktop application and the serverless package. It is the equivalent of the CLI's --log-transaction flag.
  • Some events' logging formats changed. If you are using the logs in your scripts, you need update them to match the new format. The new format is the following:
  • Server start event:
  • Before:
  • "level": "info",
  • "message": "Server started on port 3000",
  • "timestamp": "YYYY-MM-DDTHH:mm:ss.sssZ",
  • "mockName": "mockoon-demo-api"
  • After:
  • "level": "info",
  • "message": "Server started on port 3010",
  • "timestamp": "YYYY-MM-DDTHH:mm:ss.sssZ",
  • "app": "mockoon-server",
  • "environmentName": "mockoon-demo-api",
  • "environmentUUID": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  • Transaction:
  • Before:
  • "level": "info",
  • "message": "GET /test | 200",
  • "timestamp": "YYYY-MM-DDTHH:mm:ss.sssZ",
  • "mockName": "mockoon-demo-api",
  • "transaction": {...}
  • After:
  • "level": "info",
  • "message": "Transaction recorded",
  • "timestamp": "YYYY-MM-DDTHH:mm:ss.sssZ",
  • "app": "mockoon-server",
  • "environmentName": "mockoon-demo-api",
  • "environmentUUID": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  • "requestMethod": "GET",
  • "requestPath": "/testheader",
  • "requestProxied": false,
  • "responseStatus": 200,
  • "transaction": {...}
  • (Issue #1063)
  • Finally, the new logging format automatically filters out credentials from the logs. It means that if you are using the --log-transaction flag or the full transaction logging settings, the authentication keys present in the Authorization or Proxy-Authorization headers are anonymized. (Issue #688)
  • Desktop application:
  • The logs are now formatted the same way as the CLI and the serverless package (JSON). See logs standardization section above for more details. (Issue #1063)
  • A new setting is available to enable full transaction logging. (Issue #1063)
  • enable full transaction logging in the settings dialog:
  • A new context menu item is available to move an environment's data file to a new location without having to close and reopen it. (Issue #1062)
  • move environment file to a new folder:
  • The id property used to manipulate data in single resource routes (GET /res/:id, PUT /res/:id, etc.) in a CRUD endpoint can now be set to something else like "uuid", "custom_id", etc. (Issue #1041)
  • customize the crud id property:
  • You can now search for routes in collapsed folders. (Issue #960)
  • OpenAPI:
  • A bug was fixed where OpenAPI export was crashing due to an incompatibility with CRUD routes. (Issue #1066)
  • When exporting to OpenAPI format, inline bodies are now used to populate the example property (Issue #352):
  • "paths": {
  • "/test": {
  • "get": {
  • "responses": {
  • "200": {
  • "description": "",
  • "content": {
  • "application/json": {
  • "example": "{"response": "success"}"
  • Changes to templating helpers:
  • The data and dataRaw helpers are now compatible with values coming from other helpers like queryParam. (Issues #1069)
  • We added a new boolean parameter to the oneOf helper to allow the user to stringify the result of the helper. (Issues #1074)
  • The faker helper is now compatible with Faker.js methods containing a number (internet.ipv4 and internet.ipv6). (Issues #1078)
  • CLI:
  • The logs format changed to match the desktop application and the serverless package. See logs standardization section above for more details. (Issue #1063)
  • We refactored the CLI to remove the dependency to PM2, which was subject to some security vulnerabilities. Another reason for this refactoring, was that, having multiple other ways to manage running CLI instances (i.e. containers), embedding a process manager felt a bit outdated and overkill. The CLI is now easier to maintain and more lightweight. As a consequence, the following changes were made:
  • The list and stop commands were removed together with the --pname flag which was used to customize PM2's process name.
  • The --daemon-off flag was removed and running the CLI as a foreground process is now the default.
  • The dockerize command was simplified and reduced to its core promise: it will now only generate the Dockerfile and copy (or download) the provided data files next to it. Head over to the CLI documentation for more details.
  • (Issue #1081)
  • Serverless package:
  • The package now logs all events and transactions to stdout (console) in the same logging format used by the desktop application and the CLI. (Issues #1063 and #978)
  • A new option is available to enable full transaction logging. (Issue #1063)

New in Mockoon 3.0.0 (Apr 28, 2023)

  • Unified versioning:
  • We are now using unified versioning across all our packages. This means that the desktop application, the CLI, and the serverless package will all be released with the same version number. This will make it easier to know which version of the CLI or the serverless package is compatible with the latest features of the desktop application. In practical terms, these changes mean that the desktop application will now follow semver and will be released with the same minor or major version number alongside the CLI and serverless package. This starts today with the release of v3.0.0.
  • Breaking changes:
  • Mockoon's desktop application is no longer compatible with Windows 7 and 8.
  • We dropped support for Node.js v14. The CLI and the serverless package now require at least Node.js 16.
  • The Docker image is now built using node:18-alpine.
  • Desktop application:
  • Breaking change: We updated the application to the latest version of Electron. Thus, it is no longer compatible with Windows 7 and 8. (Issue #977)
  • The custom URL scheme (mockoon://) was temporarily deactivated on Linux due to a bug causing association of HTML files with Mockoon. (Issue #997)
  • We fixed a bug were the next route wasn't made active when the first one was deleted. (Issue #1014)
  • CLI:
  • Breaking change: The CLI's Docker image is now using node:18-alpine. (Issue #959)
  • Breaking change: We dropped support for Node.js v14. The CLI now requires Node.js 16 at least. (Issue #959)
  • A new flag --disable-log-to-file is available to disable the file logging. It is now the default for the Docker image. (Issue #868)
  • Our CLI's Docker image is now multi-architecture and compatible with Arm64. (Issue #670)
  • Curl was added to the Docker image to enable health checks. (Issue #945)
  • We migrated the Oclif dependency for the CLI to the latest versions. The message stating that "cli-ux" is deprecated is not present anymore. (Issue #997)
  • Serverless package:
  • Breaking change: We dropped support for Node.js v14. The package is now requiring Node.js 16 at least. (Issue #959)
  • Common changes:
  • New templating helpers:
  • Multiple helpers were added:
  • PadStart and padEnd mimicking the native JavaScript String methods. (Issue #855)
  • GetVar to access variable created with setVar dynamically. (Issue #885)
  • We also made the following improvements:
  • DateFormat is now compatible with Date objects returned by helpers such as Faker's date.recent: {{dateFormat (faker 'date.recent') 'yyyy-MM-dd'}} (Issue #1012)
  • Chores:
  • Dropping Node.js 14 support allowed us to remove the uuid dependency across all the packages. (Issue #1003)

New in Mockoon 1.23.0 (Mar 2, 2023)

  • CRUD routes:
  • We are excited to release a new long-awaited feature: the CRUD endpoint. Where Mockoon routes are independent and stateless, CRUD endpoints can generate multiple routes to perform CRUD operations (Create, Read, Update, Delete) on data buckets. Data buckets are generated when the server start, their state persisting between calls. It makes them the perfect tool to simulate small databases.
  • Head over to the CRUD routes documentation to learn everything you need to make the most of them.
  • Default listening IP addresses:
  • Mockoon desktop and CLI now listen by default to both IPv4 (0.0.0.0) and IPv6 (::) default addresses. You can also override the hostname in the desktop application in the environment settings tab:
  • Add support for OpenAPI's examples:
  • Mockoon can now create responses from OpenAPI examples during import. Considering this partial OpenAPI YAML specification file:
  • /activities:
  • get:
  • summary: List of activities
  • responses:
  • '200':
  • content:
  • application/json:
  • schema:
  • type: array
  • items:
  • $ref: '#/components/schemas/Activity'
  • examples:
  • Sports:
  • value:
  • id: 1
  • name: Basketball
  • id: 2
  • name: Volleyball
  • Music:
  • value:
  • id: 3
  • name: Guitar
  • id: 4
  • Mockoon will automatically create multiple responses from the schema and the examples:
  • WebDAV HTTP methods:
  • Mockoon now supports WebDAV's HTTP methods for distributed authoring as specified in the RFC2518 Section 8:
  • Auto-start environments:
  • We added a new setting to auto-start the environments when the application launches:
  • Improved logs interface:
  • We improved the logs interface to clarify the purpose of the delete button:
  • Small improvements and fixes:
  • The Docker image now exposes port 3000 by default when you cannot specify a port to expose (e.g. GitLab CI). You can still override the default exposed port using -p at runtime or ports inside a docker-compose configuration file. (Issue #932)
  • Fixed data buckets request helpers not being detected when imbricated in other helpers. (Issue #928)
  • A missing text/markdown content type was added to the headers auto-completion.

New in Mockoon 1.22.0 (Jan 14, 2023)

  • Breaking changes:
  • The faker templating helper is no longer stringifying arrays and objects. It can now be used with other helpers like each. (Issue #880)
  • The data and dataRaw helpers do not return the full data bucket anymore when nothing was found at a specific path. (Issue #918)
  • Routes folders:
  • You can now organize your routes into folders and sub-folders
  • his new feature allows users to better organize their routes and make their APIs more readable and easier to navigate, with a clearer hierarchy. During the development, we also reworked how the drag and drop and the filtering are handled, which should result in an overall better experience. Head over to our folders documentation to learn more about this feature. (Issue #97)
  • Cloud functions and serverless environments:
  • We published a new @mockoon/serverless package to help you run your mocks in cloud functions and serverless environments (AWS Lambda, GCP/Firebase Functions, etc.). Head over to the dedicated documentation to learn more.
  • (Issue #861)
  • Improvements:
  • The full helpers list have been added to the autocomplete menu in the body editor. (Issue #289)
  • A new dateFormat helper has been added. (Issue #873)
  • The HTTP status message (404 - Not Found) is now visible in the logs tab. (Issue #852)
  • A new status templating helper is available. It lets you customize the response status code inside a template. (Issue #894)
  • Fixes:
  • The faker templating helper is now compatible with some helpers like queryParam. (Issue #887)
  • The data and dataRaw helpers do not return the full data bucket anymore when nothing was found at a specific path. (Issue #918)
  • Templating errors are now correctly reported in the response body when they occurs during the generation of a data bucket. (Issue #866)

New in Mockoon 1.21.1 (Jan 12, 2023)

  • Data buckets containing JSON data are now correctly returned when linked to a route response. (Issue #841)
  • The dataRaw helper now correctly returns the data at the object path. Falsy values at path are also supported. (Issue #842)

New in Mockoon 1.21.0 (Oct 19, 2022)

  • New data buckets:
  • We added a new feature called "Data buckets". It's a key-value store available in each environment. Each data bucket is persistent and generated when the server starts. Data buckets can be directly linked to a route response or using one of the two new helpers: data and dataRaw. Read the documentation to learn more. This first step will make the development of CRUD and GraphQL routes easier.
  • Dialogs default directory:
  • Until now, the save and open dialogs were pointing by default to Mockoon's binary folder. It could result in data loss as the folder could be wiped on some systems during an update. The dialogs now open to the application's data folder and save their current working directory as it should. (Issue #756)
  • Templating helpers:
  • We added a new parseInt helper. (Issue #766)
  • We updated Faker.js from version 6.3.0 to version 7.6.0.
  • Fixes:
  • The date helper is now compatible with other helpers like queryParam. (Issue #781)
  • The objectId helper is now an alias for Faker.js' mongodbObjectId method. (Issue #829)
  • Serving a file with an unknown mime type now correctly revert to the environment Content-Type. (Issue #785)
  • Duplicating a route to an environment now correctly save the new route in the environment JSON file. (Issue #790)
  • ⚠️ Breaking change: setVar helper has been reworked and is not breaking anymore when used inside an each. The usage of variables is also uniformized and now requires an @. See the updated documentation for more information. (Issue #793)
  • Improvements:
  • We improved the menus resizer visibility. (Issue #729)
  • text/xml content type is now suggested in the header autocomplete menu and is correctly enabling the editor's XML syntax highlighting. (Issue #798)

New in Mockoon 1.20.0 (Aug 1, 2022)

  • Disabled rules
  • Invert the response rule operator
  • Support for properties with dots
  • Fixes:
  • We fixed a race conditions where settings were accessed before being loaded. (Issue #751)
  • Improvements:
  • The route responses menu now takes the full available width (Issue #719)
  • We enabled XML support for the application/soap+xml content type. (Issue #757)

New in Mockoon 1.19.0 (May 31, 2022)

  • CLI:
  • [BREAKING CHANGE] We removed the support for Node.js 12 as it is not maintained anymore. (Issue #702)
  • Environment files change monitoring:
  • After temporarily disabling the new environment files watcher in v1.18.1 due to an issue, we reworked this feature from the ground up.
  • It must now be manually activated in the settings and offers more choices. You can now activate the file watcher and reload the environments after validating a confirmation prompt, or automatically.
  • Improved default route response selection:
  • Defining the default response is now easier. Before this change, the default response was always the first one. Now, the blue flag indicates the default response and you can change it by clicking on the grey flags
  • New templating helpers and Faker.js update:
  • We added new templating helpers: lowercase, uppercase, and base64Decode. (Issues #655 and #625)
  • We also updated Faker.js to version 6. It offers some new helpers and locales. (Issue #716)
  • Copy an endpoint full path:
  • A new context menu entry is available to copy the full API endpoint path
  • Google Analytics removal:
  • Following the introduction of a custom privacy-friendly telemetry system last year, we removed Google Analytics from the desktop application. (Issue #713)
  • Fixes:
  • The API prefix is now correctly removed when forwarding (using the proxy mode) to a prefixed endpoint. (Issue #585)
  • Logs are now properly displayed even when Mockoon is called with malformed URIs. (Issue #689)
  • The setVar helper is now correctly working inside block helpers. (Issue #706)
  • The faker helper now returns the correct value and not only strings. It makes this helper compatible with other helpers that requires numbers, arrays or booleans to work (e.g. int, if, each, etc.). (Issue #699)
  • Misc:
  • We moved the project to a monorepo to accelerate the development and reduce the amount of manipulation we have to do when working on features. (Issue #640)
  • We also updated the CI workflows to always test the packaged desktop application when opening PRs. It will greatly reduce the amount of testing needed during a release.
  • Docs:
  • We updated the OpenAPI documentation to explain the discrepancies between the specification and Mockoon's features.

New in Mockoon 1.18.1 (Mar 6, 2022)

  • We temporarily disabled v1.18.0's automated file changes monitoring (see below) due do some unforeseen bugs (Issue #649). We will investigate and fix the issue in the next release.

New in Mockoon 1.18.0 Pre-release (Feb 28, 2022)

  • Environment files changes monitoring:
  • Mockoon now monitors for environment's files external changes and automatically reloads the interface with the new data. It's completely automated and will restart the running server if needed. (Issue #580)
  • Import/export deprecation
  • We removed the options to import/export your mock data in Mockoon's proprietary format. Since v1.16.0, importing and exporting in Mockoon's format was made mostly useless. Environment files are now easier to share "as-is" and they are supported out of the box by the CLI. Also, user feedback indicated that keeping this export option was rather confusing.
  • Here are the consequences of this removal:
  • import/export in Mockoon's format options were removed.
  • Exporting environments and routes to the clipboard (in the right-click context menu) now copy the regular JSON data, without wrapping them in the old export format.
  • The application and the CLI are still able to open old export files, but you won't be able to create them anymore.
  • Mock API samples:
  • To help you mock third party APIs in no time, we added more than 2000 new mock samples: 1Password, AWS, Giphy Mastercard, Slack, etc.
  • Enhancements:
  • Mockoon now directly streams files that do not support templating, or when templating is disabled, to improve the performance, especially the memory usage. (Issue #605)
  • The query string display in the logs has been improved. It now shows the raw query and the parameters in a more structured way.
  • Fixes:
  • dateTimeShift helper's days, months, years, etc. parameters are now compatible with helpers returning strings (queryParam, etc.). (Issue mockoon/commons-server#39)
  • Using bodyRaw without a path is now compatible with other helpers like each and allows to retrieve root level arrays. (Issue mockoon/commons-server#41)
  • Using numbers as body and bodyRaw paths, like in {{#repeat 2}}{{body @index}}{{/repeat}}, now works and returns the correct values. (Issue mockoon/commons-server#42)

New in Mockoon 1.17.0 (Nov 30, 2021)

  • UI redesign:
  • To improve some features' discoverability and declutter the interface a bit, we redesigned the main header. We also polished the interface a bit here and there.
  • Here are the most significant changes:
  • New header design:
  • We transformed the main header into a new menu with tabs to make the proxy mode and logs more easily discoverable. We also split the environment settings into three new sections: the environment headers, the proxy options, and the environment settings.
  • The environment's information previously available in the header are now in the "Settings" tab.
  • Environment's menu improvements:
  • We made small adjustments to the environment menu:
  • You can edit the environment's name directly in the menu.
  • We removed the "CORS" icon as the option is always enabled and moved the "HTTPS" icon next to the URL.
  • The "Truncate long paths" option in the application settings (ctrl+comma) also applies now to the environment menu. If enabled, environment URLs won't be truncated anymore.
  • new-api:
  • Headers and rules "click-to-confirm" delete button
  • Headers and rules lists now uses a click-to-confirm delete button:
  • Responses list improvements:
  • The route responses menu is now split into two lines as it was becoming too cluttered.
  • File and body information display improvements:
  • We reorganized the "Status & body" tab. More precisely, we removed the redundant Content-Type information and replaced it with a small "footer" under the body editor. This footer will always display the effective Content-Type taking the order of precedence into account:
  • environment headers → file mime type → route headers
  • Ability to provide custom TLS certificate:
  • You can now provide a custom TLS certificate to serve your mocks over HTTPS. Mockoon still uses the same self-signed certificate as before if you don't provide a custom one.
  • New response rules for cookies:
  • A new response rule is available to check a cookie's value or presence:
  • New templating helpers:
  • New Handlebar helpers are available: join, len, gt, lt, gte, lte, eq, toFixed, round, stringify, slice. Head over to the helpers documentation to learn how to use them.
  • Misc:
  • When creating a new environment, the default name won't be "New environment" anymore but will be taken from the chosen environment's file name.
  • Cookie domains are now removed when forwarded with the proxy mode.
  • Bug fixes:
  • Fixed setVar helper which could not handle Object, 0 or Arrays.
  • Fixed switch/case helpers which wouldn't work properly with number.
  • We switched from using a (heavy) icons font to using inline SVG to solve the icons flickering issue when loading the application.

New in Mockoon 1.16.0 (Oct 14, 2021)

  • New storage system
  • The main feature of this release is the new storage system that allows for more flexibility and easier API sharing.
  • The new system works more or less like any other file editor. It stores environments separately and lets you close and open them from anywhere on your hard drive.
  • So, what exactly happened during this update? Mockoon split Your existing data file located in the application data folder into as many files as you had environments. These files were created in the same storage folder with incremental names: environment-0.json, environment-1.json, etc.
  • You can now move these files anywhere on your hard drive and open them from there.
  • Multiple benefits from this change:
  • you can now more easily share your environments with your coworkers by saving them in a Git-tracked folder. There is no need to import/export every time there is a change anymore.
  • we added an environment schema validation to ensure that the environment you load is valid and does not break the application behavior.
  • Body files relative path resolving:
  • Mockoon will now try to resolve your body files relatively to the environment's file location. It allows you to store body files alongside the environment file and share them with your coworkers without having relative or absolute path issues.
  • New buttons and menu entries:
  • Following the new storage change, we added several new buttons and options to allow you to manage your environment files.
  • You can create a new environment or open an existing one using the two buttons at the top of the environment menu
  • You can now close one environment using the context menu
  • There is a new context menu entry you can use to locate the environment file on your computer
  • Most of the actions tied to the environments also changed. You will now get prompted to choose a folder location for your new environment every time you create, duplicate, or import.
  • New mock samples:
  • We added more API samples to help you start working in no time. You can find them on our website.
  • Starting with this version (1.16.0), you can load them directly in Mockoon by clicking on the "Open" buttons on the page.
  • Environment menu redesign:
  • We reverted last year's change that made the environments' menu collapsible. This menu was only showing the first two letters of the environment's name. We listened to your feedback, and we decided to revert this change and go back to a resizable menu. We tried to keep it as compact as possible, considering that most users have no more than one or two environments. Let us know what you think!
  • XML support:
  • Response rules and body templating helper now support XML in entering requests. See the documentation for more information.
  • New rules operators:
  • Two new rules operators, "null" and "empty array", were added to allow you to check against null values and empty arrays in bodies, query params, etc.
  • Route filtering shortcuts:
  • We added some keyboard shortcuts to the route filtering: Cmd or Ctrl + Shift + F to focus, Esc to clear the field. (Issue #451)

New in Mockoon 1.14.1 (May 19, 2021)

  • Allowing duplicated headers (issue #318) was causing some issues with the pre-flight OPTIONS calls and breaking the route headers precedence over environment headers. Duplicated headers are now limited to the Set-Cookie header. (Issue #480)

New in Mockoon 1.14.0 (May 17, 2021)

  • Features:
  • Status codes (Issue #199):
  • We added some missing status codes to the dropdown, but more importantly, you can now enter custom status codes. Even very invalid ones like 999.
  • Sequential responses (Issue #459):
  • A new option is now available to serve different responses sequentially.
  • In the below example, Mockoon will answer with 200 ? 404 ? 500 ? 200 ? 404... and so on. The sequence gets reset after restarting the server.
  • Head over to the sequential responses documentation to learn more about this feature.
  • Request number response rule (Issue #459)
  • A new type of rule, "Request number", is now available. It allows you to serve a specific response depending on the index (number) of the entering requests. As for the sequential responses feature, it gets reset when restarting the server.
  • Head over to the response rules documentation to learn more about this feature.
  • Misc:
  • A new baseUrl helper has been added which returns the request's base URL (without the route path): {protocol}://{hostname}:{port}/{prefix}. (Issue mockoon/commons-server#7)
  • A new option has been added to prevent forwarding of the API prefix when the proxy mode is enabled. (Issue #237)
  • Improvements:
  • To improve the application stability, only one instance can run at a single time. Running a second instance of the application will focus the running instance if any. (Issue #455)
  • Multiple headers with the same name are now supported everywhere (route headers, environment headers, proxy request/response headers). This may be a non-standard way of sending the headers (vs comma-separated values) but a common one, especially for the Set-Cookie header. (Issue #318)
  • We added more suggestions to the header names and values dropdowns to help you mock faster!
  • Thanks to work on issue #199, we improved the look and feel of the HTTP methods dropdown with improved hype pastel colors.
  • "Port is invalid" message has been updated to "Port is invalid or access is denied" to give more hints about the potentially reserved ports on Windows. (Issue #463)
  • Fixes:
  • We updated the Faker.js library to its latest version. This indirectly solved the issue with 'internet.avatar' URLs returning a 403. (Issue mockoon/commons-server#1)
  • Having a response with empty rules but an AND operator does not interrupt the rules evaluation and does not serve the wrong response anymore. (Issue mockoon/commons-server#6)
  • Route path and prefix duplicated slashes are now correctly deduplicated when running the server. (Issue mockoon/commons-server#9)

New in Mockoon 1.13.0 (Apr 21, 2021)

  • Features:
  • Routes can now be filtered by path and documentation (Issue #257)
  • Three new string manipulation helpers are now available: indexOf, includes, substr. See documentation for more information. (Issue #413)
  • Fixes:
  • Fix setVar helper not working in block helpers like repeat. (Issue #429)
  • Add a new third parameter (boolean) to the body helper to returns the stringified value even if it's a primitive. (Issue #397)
  • Add a new third parameter (boolean) to the queryParam helper to returns the stringified value. (Issue #418)
  • Proxied binary bodies are no longer converted to UTF-8 strings and are now forwarded "as-is". (Issue mockoon/commons-server#3)
  • When switching route responses the body undo state does not contain other routes' body content anymore. (Issue #309)
  • Adding a trailing slash to the API prefix do not returns 404s on all endpoints anymore. (Issue #422)
  • Misc:
  • Mockoon is now more secure by a combination of enabling Chrome sandboxing and Electron context isolation. We also disabled Node.js integration and stopped using the remote module in Electron's renderer process. These best practices have been pushed and enabled by default by Electron's team in the most recent versions. We took it on ourselves to try to follow them all and rewrote part of the application architecture. Aside from the improved security and prevention of future vulnerabilities like XSS and RCE, we also saw slightly better performances overall. (Issue #349)
  • max-http-header-size which was limited to 8kb is now limited to 16kb thanks to an update to Node.js v14. (Issue #442)

New in Mockoon 1.12.0 (Mar 4, 2021)

  • New features:
  • Three new helpers are available:
  • concat to create string from multiple strings and variables. (Issue #391)
  • {{ concat 'value1' 2 'value3' ... }}
  • setVar to create string values to be reused elsewhere in the template. (Issue mockoon/commons#8).
  • {{ setVar 'varname' 'value' }} {{ varname }}
  • dateTimeShift to shift a date from x days, months, etc. (Issue #355)
  • {{ dateTimeShift date='2021-01-01' format='yyyy-MM-dd' years=1 months=1 days=1 hours=1 minutes=1 seconds=1 }}
  • Please check the documentation for more information on how to use these helpers.
  • Body response rules can now be used to match against the entire raw body. To use this feature, just keep the modifier empty. (Issue #271)
  • You can now duplicate routes from one environment to another. (Issue #308)
  • Improvements:
  • Route headers and rules tabs now show the totals of each. (Issue #299)
  • OpenAPI default responses are now considered as 200 and will get a body example from the available schema. (Issue #378)
  • OpenAPI parser is now compatible with Content-type that contains a charset application/json; charset=utf-8. (Issue #379)
  • Bug fixes:
  • Fixed a crash when importing OpenAPI specification files with no servers property. (Issue #415)
  • Fixed a bug when importing or duplicating an environment with no routes. (Issue #416)
  • Some users reported a bug where the main window cannot be maximized in Debian with XFCE. We weren't able to reproduce the issue but we tried to fix it anyway with some black magic. Let us know if things improved or not. (Issue #357)
  • Fixed a bug in the response rules interpreter when comparing against null values. (Issue mockoon/commons#16)
  • Fixed API prefix and endpoint paths leading and duplicated slashes not being sanitized anymore. (Issue #421)
  • The splash screen transparency issue on Linux is no longer there due to use of a new splash screen. (Issue #364)
  • Misc:
  • Fine tune some settings to improve the performance. (Issue #376)
  • Migrated from Angular 8 to 11. (Issue #358)

New in Mockoon 1.11.0 (Nov 12, 2020)

  • Fix automated tests not running correctly due to the newly added splash screen. (Issue #341)
  • Fix broken layout in some rare cases due to usage of responsive row/col. (Issue #365)

New in Mockoon 1.10.0 (Sep 16, 2020)

  • New features:
  • A JSON body sample is now generated during a Swagger/OpenAPI file import when a schema is present. (Issue #288)
  • Response rules can now be interpreted as OR or AND. (Issue #201)
  • Rules can now check JSON bodies number and boolean values. (Issue #321)
  • Two new helpers are available in the templating system: newline, which inserts the newline character "n", and base64 inline or block helper to encode all your stuffs. For more information, please refer to the official documentation. (Issue #331)
  • Bug fixes:
  • Fix an issue where some helpers (queryParam, body, etc) couldn't be used as switch helper value. (Issue #325)
  • Fix crash when importing Swagger files where the host property is missing. (Issue #326)
  • Binary files are now properly sent instead of being converted to strings. (Issue #324)
  • Windows-like file path (with backslashes) are now compatible with templating helpers C:UsersusernameDesktop{{ urlParam 'id' }}.json. (Issue #323)
  • The environment's logs layout is not broken anymore when displaying long binary bodies. (Issue #335)
  • Fixed a silent error when export dialog was canceled. (Issue #337)
  • UI improvements:
  • Export menu items are now disabled when there is no environment to export. (Issue #336)
  • Route path input now autofocus after adding a new route. (Issue #334)
  • Mockoon has a new fancy loading screen ?? to avoid content flickering during load.
  • Misc:
  • Work has started on the CLI (mainly refactoring), but shhh ?? don't say it too loud, there is still a long way to go!

New in Mockoon 1.10.0 Pre-release (Sep 14, 2020)

  • New features:
  • A JSON body sample is now generated during a Swagger/OpenAPI file import when a schema is present. (Issue #288)
  • Response rules can now be interpreted as OR or AND. (Issue #201)
  • Rules can now check JSON bodies number and boolean values. (Issue #321)
  • Two new helpers are available in the templating system: newline, which inserts the newline character "n", and base64 inline or block helper to encode all your stuffs. For more information, please refer to the official documentation. (Issue #331)
  • Bug fixes:
  • Fix an issue where some helpers (queryParam, body, etc) couldn't be used as switch helper value. (Issue #325)
  • Fix crash when importing Swagger files where the host property is missing. (Issue #326)
  • Binary files are now properly sent instead of being converted to strings. (Issue #324)
  • Windows-like file path (with backslashes) are now compatible with templating helpers C:UsersusernameDesktop{{ urlParam 'id' }}.json. (Issue #323)
  • The environment's logs layout is not broken anymore when displaying long binary bodies. (Issue #335)
  • Fixed a silent error when export dialog was canceled. (Issue #337)
  • UI improvements:
  • Export menu items are now disabled when there is no environment to export. (Issue #336)
  • Route path input now autofocus after adding a new route. (Issue #334)
  • Mockoon has a new fancy loading screen to avoid content flickering during load.
  • Misc:
  • Work has started on the CLI (mainly refactoring)

New in Mockoon 1.9.0 (Jul 24, 2020)

  • Templating system:
  • Dummy JSON helpers ({{firstName}}, {{date}}, etc) that could be used in the body have been replaced by Faker.js. This brings a lot more helpers together with many locales that can be selected in the settings. All the old helpers remain compatible and are automatically linked to their Faker.js equivalent. Faker.js helpers use the following syntax: {{faker 'company.companyName'}}, {{faker 'name.firstName'}}, etc (Issue #293)
  • Improvements to the body helper:
  • JSON Objects and arrays can now be retrieved from the entering request's body with templating helpers and added to the response body. (Issue #291)
  • The full request's body can now be retrieved with the body helper used with no parameter: {{body}}. This is compatible with any Content-Type. (Issue #276)
  • The body helper has been improved for x-www-url-encoded bodies. Objects and arrays are now supported. (Issue #290)
  • Improvements to the queryParam helper: as for the body helper, the queryParam helper can now retrieve paths, arrays, objects, or the full query params object. (Issue #265 )
  • Templating can now be disabled for bodies and files content. Head up to the new route response's "Settings" tab. (Issue #129)
  • For more information about the templating system, please refer to the official documentation.
  • Errors feedback
  • Application errors feedback has been greatly improved especially for JSON content (Issue #253):
  • All errors, including templating errors, are now reported in the response body.
  • Erroneous JSON bodies are now sent in the response to make debugging easier.
  • Incoming and outgoing bodies can now be easily viewed in an editor with linting activated in the environment logs ("clock" icon, in the upper right corner). This is especially useful to view the outgoing body built with the templating helpers.
  • Templating system errors are now better reported, including for templating used in headers or file path.
  • Other improvements:
  • Features:
  • Route responses can now be duplicated by clicking on the "copy" button next to the route response's tabs. (Issue #250)
  • UI improvements:
  • Routes and environment logs menus can now be resized. These preferences are automatically saved. (Issue #104)
  • Scrollbars now have a lighter color to make them more visible. (Issue #297)
  • The "Open in browser" button next to the route path is now always visible but disabled for non GET routes. (Issue #287)
  • The file browsing button use has been clarified by adding a tooltip. (Issue #254)
  • Scrolling of environments and routes menu has been disabled when duplicating. (Issue #296)
  • Bug fixes:
  • Data storage has been improved to better handle crashes and report errors. (Issue #313)
  • When serving a file, the environment's Content-Type could override the file's detected mime type. A route Content-Type can still override the detected mime type. Order of precedence: Route's Content-Type > File's mime type > Environment's Content-Type. (Issue #295)
  • Application was crashing when using some templating helpers ({{boolean}}). (Issue #285)
  • Fixed a bug when binary bodies were truncated for environment logs. (Issue #294)
  • The route responses dropdown is now scrollable should you have a lot of items. (Issue #305)
  • Environment logs response and request tabs do not scroll with the content anymore. (Issue #311)
  • Body editor's tab size is now set to 2 spaces by default. It was previously set to 4, which was inconsistent with other options using 2 spaces. (Issue #312)
  • Misc:
  • Demo environment has been updated to better show Mockoon's capabilities. (Issue #300)
  • Release notes are now shown on startup after an update. (Issue #302)
  • The official website has a new versioned documentation regrouping the old "tutorials". It will be frequently updated to reflect the application evolution and add new topics.
  • Code enhancements/developer experience:
  • Environment logs system have been refactored to easier future developments.

New in Mockoon 1.8.0 (Apr 17, 2020)

  • Features:
  • Add support for import/export of Swagger and OpenAPI formats #86
  • Environments menu is now smaller and collapsed by default #173 Thanks to @JoshMLeslie
  • Specific proxy headers can now be sent to proxied servers and added to their responses #223 Thanks @neocodegs
  • Improvements:
  • A new setting is available to show the complete route path in the menu instead of a truncated version #227 Thanks @johnwest80
  • Add a templating helper to read cookies content #235 Thanks @sleepypikachu
  • Duplicated routes and environments are now inserted after the original instead of the end of the list #239 Thanks @sleepypikachu
  • 404s now returns global environment headers #136 Thanks @abiodunjames
  • Proxied responses returning a 404 now correctly propagate proxied environment headers and proxy headers #240 Thanks @abiodunjames
  • Etag header has been removed to avoid browser caching #244
  • ExpressJS x-powered-by header has been removed
  • Environment logs body section is now opened by default #200
  • Some application logs can now be found in the Mockoon data folder (available from the Help menu) in the logs folder #262
  • Add missing HTTP status code 418 #270
  • Increase route responses dropdown width #249
  • Bugfixes:
  • Content-Type was fetched in a case sensitive manner which could lead to JSON parse errors when the route's Content-Type was different from environment's #243
  • Using native actions menu could crash the application when no environment was present #233
  • Environment logs menu icons are not hidden anymore when long routes are displayed #238 Thanks @sotcha
  • Increase server timeout to 1 hour to allow the setup of long latencies #258
  • Fix rules always returning true for regexes when the target (body, ...) was undefined #259
  • Fix bug with automatically mocked routes hanging when Set-Cookie header was involved #229
  • Fix race conditions between environments migration and settings loading #283
  • Code enhancements/developer experience:
  • A Docker image has been created to easier Arch Linux repository updates #231 Thanks @Spissable
  • Update application dependencies, review imports, add missing types #275
  • Reduce the number of events sent to Google Analytics to avoid exceeding the free tier #277

New in Mockoon 1.7.0 (Dec 17, 2019)

  • Features:
  • Migrations are now played on each imported environment independently #21
  • File export is now fully compatible with a clipboard export (clipboard content can be pasted in a JSON file and imported) #102
  • Improvements:
  • Added a label to better identify route responses #170
  • Data are now exported without UUIDs to easier sharing #216
  • Avoid possible crashes by preventing using a migrated environment on an older Mockoon version #218
  • Added a link in the help menu to open the application data folder #184
  • Added a keyboard shortcut to export all environments to JSON #134
  • Bugfixes:
  • Fixed a bug where data were wiped on the second launch of a fresh install #217
  • Support Content-Type with charsets (or any additional information after a ;) that were preventing rules to be triggered #214
  • Development:
  • Add Prettier for better code formatting

New in Mockoon 1.6.0 (Nov 14, 2019)

  • Features:
  • Create mock routes from environment logs entries (proxied or not) #139 Thanks @gabrielperes97
  • Add possibility to enable/disable a route #106 Thanks @gabrielperes97
  • Environment log's bodies from entering request and outgoing responses can now be truncated to desired length in the settings #186 Thanks @gabrielperes97
  • Improvements:
  • Add an icon next to the first route response to better indicate the default one #171
  • Update to Electron 7 #183
  • New environments (created or duplicated) get next available port or a random one instead of default 3000 #192 Thanks @gabrielperes97
  • Mockoon is now available on Arch Linux repository #202 Thanks to @Spissable
  • Bugfixes:
  • Fixes a bug where UI wasn't refreshing after selecting a file to serve #189
  • Fixes a bug where adding/removing a route wasn't displaying the "restart needed" indicators #187
  • Hide two macOS specific menu entries on Windows and Linux #193
  • Development:
  • Automate binaries build for the 3 targeted platforms #181

New in Mockoon 1.5.1 (Oct 17, 2019)

  • Bugfixes:
  • Correct bug introduced by v1.5.0 where duplicated routes responses shared some UUID #180

New in Mockoon 1.5.0 (Oct 8, 2019)

  • Features:
  • Add multiple responses per route with possibility to set triggering rules #75
  • Add Mockoon's responses log side by side with entering requests #155 & #138 Thanks @gabrielperes97
  • Linux users can now download Mockoon in deb and rpm formats alongside AppImage. Mockoon is also available on Snap Store. #168
  • Improvements:
  • Update UI to reflect server binding on multiple network interfaces #99
  • Update "someOf" helper to return a string or an array #131
  • Make documentation field less confusing by moving it down and rewriting the placeholder #140
  • Replace old deprecated wiki "help" menu link with Spectrum community link #135
  • MacOS binary has been notarized, which should easier the installation on macOS Mojave #71
  • Bugfixes:
  • Correct bug where body formatting option was not propagating the changes immediately #147
  • Misc:
  • Add multiple responses tutorial on the official website https://mockoon.com/tutorial/multiple-route-responses
  • Update request logs to reflect new responses log feature https://mockoon.com/tutorial/incoming-requests-logs
  • Development:
  • Update contribution guidelines
  • Add more NPM scripts for local development

New in Mockoon 1.4.0 (May 14, 2019)

  • Improvements:
  • Add warning next to the path input to prevent accidental declaration with query params #88
  • Allow environment headers to override automatic OPTIONS CORS headers #85
  • Add JSON pretty print in body #103 (Thanks @vankeer)
  • Support Hide / Hide Others / Settings standard shortcuts on macOS #93 (Thanks @axc450)
  • Add support for current date time in templating helpers (with now helper) #96
  • Add support for x-www-form-urlencoded params in body templating helper #116
  • Improve JSON export formatting #123 (Thanks @axc450)
  • Bugfixes:
  • Fixed bug where an error would appear if a user cancels a file select during export #107 (Thanks @axc450)
  • Misc:
  • Application was completely rewritten to use custom Redux-like state management. With this, Mockoon is more stable and app behavior is more predictable #95
  • Development:
  • Use local test data in ./tmp folder instead of default user folder #109
  • Add more functional tests

New in Mockoon 1.3.0 (Dec 17, 2018)

  • Features:
  • Add new environment's headers that are applied to all routes #56
  • Add route documentation field #63
  • Some files with specific mime types will get their content parsed for templating #80 ( See templating tutorial )
  • Improvements:
  • File input field is now editable and supports templating #52 ( See templating tutorial )
  • Add search box in body editor #79
  • Automatically select the first item in autocomplete list and correct some display and usability bugs
  • New environments will be created with global JSON Content-Type but no Content-Type for routes
  • Make routes with spaces work when request in encoded #73
  • Added option to add CORS headers to new environment headers #56
  • Some minor improvements to the interface mainly for readability
  • Allow relative path for files thanks to editable file input #84
  • Bugfixes:
  • Correct crash when declaring routes with invalid regex syntax
  • Remove links in changelog modal which were loaded inside Electron's main window
  • Solve Linux AppImage icon not showing #72
  • Misc:
  • Start adding functional tests with Spectron for more stability
  • Add more tutorials on the official website: templating and headers

New in Mockoon 1.2.0 (Oct 29, 2018)

  • Improvements:
  • Update all dependencies (Electron 3 shipping with Chrome 66 and Node.js 10, Angular 6)
  • Allow parsing of entering request's body event if Content-Type has not been set to JSON #64 & #65 Thanks @alonbhaim
  • Enable templating in header values #51 and on any body types (text, HTML, JSON, etc)
  • Display version changelog in a modal when clicking on version number
  • Bugfixes:
  • Routes reordering wasn't saved if no other update occured on an environment
  • Routes weren't assigned an UUID upon creation which resulted in reordering errors
  • Correct bug where body helpers were outputting[object object] when no default value were provided #66
  • Display a proper error message and alert when using a templating helper that does not exists instead of failing silently
  • Misc:
  • Mockoon is now available on Homebrew for our macOS friends! Just type brew cask install mockoon.
  • Added a Code of conduct
  • Started writing some contributing guidelines and help
  • Official website has now more content with some tutorials (and more to come)!

New in Mockoon 1.1.0 (Sep 26, 2018)

  • Improvements:
  • Allow text selection in request logs #54
  • Make UI a little bit lighter to improve readability #46
  • Bugfixes:
  • Correct body helper parsing error when request body was not JSON #59
  • Correct body not being sent in proxy mode #60
  • Correct typos #57 Thanks @mivanov
  • Correct bug when trying to pass an invalid Content-Type
  • Correct broken analytics tracking since release v1.0.0

New in Mockoon 1.0.0 (Aug 24, 2018)

  • Features:
  • Import/Export: All environments can now be imported and exported in a file and each environment and route can be "exported" to clipboard and imported from clipboard (#7)
  • Requests log: All entering requests are now logged in each environment (#15)
  • Improvements:
  • Support for OPTIONS requests has been added together with a new environment setting to toggle automatic CORS handling (#40) Wiki Page
  • Content-Type handling has been completely rewritten and is now managed by the Headers tab which allows full control (#34) Wiki Page
  • Environments and routes can now be reordered with a simple drag and drop (#41)
  • Some new helpers were added to the JSON templating (oneOf #36, someOf #36, switch #35 and body #47) Wiki Page
  • queryParam and header templating helpers can now have a default value (#44 thanks @nrdobie)
  • Multiple consecutive slashes are now rewritten to single slash (no redirection occurs) (#45)
  • Bugfixes:
  • Corrected jumping cursor bug for some fields (route path) (#39)

New in Mockoon 0.4.0 Beta (Apr 25, 2018)

  • Features:
  • JSON body has a new templating system (#3).
  • which can also react to request parameters with specific helpers (#4)
  • Improvements:
  • Body length now extends to full height #30
  • JSON parsing errors are not better reported
  • Bugfixes:
  • Error handling when serving deleted files has been corrected

New in Mockoon 0.3.0 Beta (Nov 20, 2017)

  • Features:
  • Proxy mode (#17): if activated all non defined routes are redirected to the specified URL
  • HTTPS support (#10): Mockoon now support HTTPS with a self signed certificate
  • Added an environment settings tab to set up proxy and HTTPS modes
  • Added a welcome screen with analytics opt out (#14 #18)
  • Added an application settings screen (currently only with analytics opt out)
  • Improvements:
  • Mockoon have now better and more visible tooltips (#13)
  • Bugfixes:
  • Deleting / adding routes now triggers the "environment needs refresh warning" (#19)
  • File download improvement, should correct corrupted files bug (#22)

New in Mockoon 0.2.0 Beta (Oct 2, 2017)

  • move route deletion buttons in context menus #11
  • add duplicate environment/route feature #1
  • add keyboard shortcuts #5
  • Add custom headers autocomplete #2
  • Correct navigation bug when removing environments/routes
  • automatically scroll when adding custom headers at bottom

New in Mockoon 0.1.1 Beta (Oct 2, 2017)

  • UI small improvements
  • rework environments menu to make route prefix more obvious
  • prevent page scrolling when using mouse wheel in number inputs
  • enable copy paste on MacOS
  • auto scroll envs and routes menu to bottom when adding items

New in Mockoon 0.1.0 Beta (Oct 2, 2017)

  • Mock an unlimited number of environments with unlimited number of routes
  • Run multiple mock servers in parallel
  • Route regex supported (/.*, /[a-z]{3}, ...)
  • Support all HTTP codes and methods
  • Built-in support for OPTIONS pre-flight requests
  • Add unlimited custom headers
  • Environment / route level latency simulation
  • Multiple body types
  • Support file download with automatic mime type detection
  • Rich text editor for body content
  • Real-time auto save