miragejs VS json-server

Mirage JS GitHub Repository

For the styles, I'll be using TailwindCSS. To simulate API requests Mirage JS will be used, which is a very easy to use and useful API mocking library. To call this API, we're going to use Fetch.

during development we use mirage JS to spin up an in-browser mock server which returns mock data for any API endpoints not currently implemented by the real backend. during integration testing we configure this server to return mock data for all API endpoints in the system, giving us a fixed environment against which our tests can run. test suites can be run in parallel since each time a playwright page is opened a new copy of the webapp, and thus a new copy of the mock server, is launched. these integration tests run whenever a frontend PR is opened or updated.

Mirage JS is specifically built for this purpose as well. It‘s a frontend JavaScript library meant for mocking backend APIs. https://miragejs.com/

We use miragejs https://miragejs.com/

The best case scenario you would be using something like MirageJS, MSW, or even JSON Server, but mocking fetch is always an option.

Mirage JS is pretty useful and allows you to create complex testing scenarios with its embedded db. Useful when you have relationships between your models.

Mirage JS: Mirage JS is an API mocking library that lets you build, test, and share a complete working JavaScript application without having to rely on any backend services.

JSON Server

Our backend will be little more than a two-way translation layer between the database and the user interface (UI). Later in this post we will identify other responsibilities of a backend but our implementation will be kept simple to demonstrate the fundamental machinery and concepts. It is worth noting the backend comes in two parts, web server and application server. Both json-server and Express are able to facilitate these roles from the same URL. This is very useful for our tutorial because we do not have to configure the server to manage Cross-Origin Resource Sharing (CORS). It is quite typical for production systems to separate these server roles for all sorts of good reasons but for now it would just create an additional complication.

JSON-Server creates fake REST API with a minimum amount of configuration, it provides a simple way to create mock RESTful APIs and easily define the required endpoints, allows easy definition of the data schema in a JSON file and can serve as a reference for each figure in the project.

I thought about usingJson Server (hosting the repo with the words on Github to begin with), Googlesheets, or maybe Firestore (i would prefer not to use it ,to avoid extra costs just in case it gets a reasonable amount of users). It isnt a big app so i just want a simple solution for storing the words and fetching them.

There is https://github.com/typicode/json-server that is really useful for that matter

JSON server https://github.com/typicode/json-server