You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be a bit divisive, but until mirage uses msw for request mocking (or at least stops using pretender), I don't think we should encourage mirage's usage.
MSW is bigger, more people looking at it improving it, whereas pretender is stagnant: https://npmtrends.com/msw-vs-pretender
(And i wouldn't consider pretender complete)
MSW supports graphql
with MSW, you dubug requests as if you didn't have mocking set up at all, in the Browser's network inspector (worlds better than pretender's logging)
MSW's data doesn't count against your build time because mocks and all that are 'just in the public folder' (though, you can still define in-bundle mocks for tests and stuff)
MSW doesn't patch globals, intercepts all requests if you want (the primary advantage of living in a service worker)
This may be a bit divisive, but until mirage uses msw for request mocking (or at least stops using pretender), I don't think we should encourage mirage's usage.
MSW is super easy to setup, and they have their own data library, too: https://github.com/mswjs/data
Here is an 8 commit tutorial for setting up MSW: https://github.com/NullVoxPopuli/ember-msw-development/commits/main
The text was updated successfully, but these errors were encountered: