msw-storybook-addon VS mock-requests

As mentioned, we'll be using the MSW addon, which stands for: "Mock Service Worker", it adds a service worker that will intercept and mock our requests.

If data is fetched through the API, https://github.com/itaditya/msw-storybook-addon

I wrote mock-requests before MSW came out. It was, to my knowledge, the first dev-friendly mocking library out there that didn't involve setting up a separate server yet still allowed dynamic responses. Since MSW came out, I still think mock-requests has a better and simpler API but MSW allows you to see the network request in the browser's dev tools which is super nice IMO.

I'd mock the network responses from the source. Others already mentioned MSW, but I personally like mock-requests better. I don't need to use a complex config nor chained methods, I still get dynamic responses based on request payload, and I can mock the entire app's requests in a single config object (harking back to not needing complex configuration logic or chained methods).

The companies I worked at were using mock-requests to help them with this and it greatly simplified their testing environment. A single call in a test-setup file meant all network calls for all flows were suddenly mocked and accessible for both unit testing and development when servers were down. I'd highly recommend checking it out!

Feel free to check out the in-depth ReadMe, install, see the JSDoc, source code, or check out the React demo.