Skip to main content
Version: Next

Organizing files


When the server is started for the first time, it will create a configuration file and a scaffold folder containing some examples of routes and collections.

├── mocks/
│ ├── routes/ <- DEFINE YOUR ROUTES HERE
│ │ ├── common.js
│ │ └── users.js
│ └── collections.json <- DEFINE YOUR COLLECTIONS HERE
  • The server loads all files in the mocks/routes folder, which must contain the route definitions.
  • The mocks/collections.* file is used to define collections of route variants.
  • The server watches for changes in all files in the mocks folder, so changing a file will immediately update the mocked API.

Collections and routes can also be defined programmatically. Read the Javascript integration chapter for further info.

Defining routes

The server searches for all files in the mocks/routes folder, including subfolders, and load their content as routes. So, every file in that folder must export an array of routes.

In the folder, you can organize the files in the way you want. As a suggestion, you could create a different file for each API entity, and a different folder for each API domain. This would help to maintain your routes organized. For example:

├── customers/
│ ├── addresses.js
│ └── users.js
└── sales/
├── orders.js
└── products.js

Remember that every file inside the /routes folder must export an array containing Mocks Server routes.

Defining collections

The server reads the mocks/collections.* file and loads its content as collections. The file extension can be .js, .json, .yaml or .yml (and even .ts, read the using Babel guide for further info).


The mocks/collections.* file must export an array of Mocks Server collections.

Supported file formats

All route files and collections file by default can be defined in JSON, YAML or JavaScript, using any of the next extensions:

  • .js
  • .json
  • .yaml or .yml

.ts files are also supported when Babel is enabled and configured properly

└─ mocks/
│ ├── common.js
│ └── users.js
└── collections.json <- DEFINE YOUR COLLECTIONS HERE

Other files and folders

You can create other files and folders in the mocks folder, Mocks Server will simply ignore them. So, for example, if you want to maintain the data you use in your routes separated from the definition of the routes theirself, you could create a data folder, and import it from the route files.

├── mocks/
│ ├── data/
│ │ └── users.js
│ ├── routes/
│ │ └── users.js
│ └── collections.json
└── mocks.config.js
module.exports = [
id: 1,
name: "John Doe"
id: 2,
name: "Jane Doe"

Hot reloading

Every time a file in the mocks folder is changed (including custom files and folders outside the routes folder), Mocks Server will reload everything automatically.

If any file contains an error, the server will add an alert, and you will be able to see the error in the interactive CLI or using any of the other integration tools.

Interactive CLI alerts

The alert will be removed automatically when the file containing the error is fixed and saved again

Interactive CLI

Good practices

Use descriptive ids

We strongly recommend to assign very descriptive ids to the routes, variants and collections, because they will be used afterwards in the CLI, the REST API, and all other available integration tools.

A good pattern for assigning an id to a route can be [method]-[entity], as in get-users, get-user, etc.

For assigning an id to the collections, we recommend to maintain a base collection named as standard, base, or default. The rest of collections should extend from it (at least indirectly), and their ids should be a short description of the collection behavior, for example:

"id": "base",
"routes": ["get-users:all", "get-user:success", "create-user:success"]
"id": "users-errors",
"from": "base",
"routes": ["create-user:error", "get-users:error"]
"id": "users-with-long-name",
"from": "base",
"routes": ["get-users:long-names", "get-user:long-name"]