Question 1

How do I add authentication to Dyson mock server?

Accepted Answer

Dyson doesn't have built-in auth; you need to implement custom Express middleware to handle tokens or headers, as shown in the custom middleware section of the README.

Question 2

Dyson vs JSON Server for API mocking?

Accepted Answer

Dyson excels at dynamic, parameter-driven responses with complex logic, while JSON Server offers a simpler fake REST API with a file-based database. Choose Dyson for flexibility, JSON Server for ease.

Question 3

Can Dyson simulate API errors or delays?

Accepted Answer

Yes, use the delay property for latency and custom status middleware for error codes, like setting res.status(404) based on parameters, as demonstrated in the README.

Question 4

How to integrate Faker.js with Dyson?

Accepted Answer

Install Faker.js, then call its functions in your template objects, e.g., name: () => faker.name.findName(), exactly as shown in the introduction example.

Question 5

Is Dyson suitable for GraphQL mocking?

Accepted Answer

Only with additional setup; you must install dyson-graphql and configure render methods, as outlined in the GraphQL section, making it less straightforward than dedicated tools.

Question 6

How to handle file uploads in Dyson?

Accepted Answer

File uploads require custom render methods to access req.files, as briefly mentioned in the README, but it's not a core feature and needs manual implementation.

dyson

What is dyson?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions