blacksheepcode
msw
blacksheepcode | msw | |
---|---|---|
10 | 150 | |
2 | 14,914 | |
- | 1.9% | |
8.1 | 9.2 | |
about 2 months ago | 2 days ago | |
MDX | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
blacksheepcode
- [Question] Recommendations for an agnostic state management?
-
REDUX or ZUSTAND?.
My workaround has been to adopt a scaffold, , which I call a 'Hook Provider' pattern, essentially injecting your data selectors/updaters via context. See here for details.
-
Replacing redux with custom hooks and react hooks
I have a blog post and code repo with specific details here.
-
How to test custom useFetch hook in Jest
Now, for testing components that use this useDataFetch function, you would also want to be able to not use the real data fetching functions. In order to do that, those functions should be provided via context, in a pattern called dependency injection. I write about it here
-
What is the best state management library?
I write about it here and here
- Best practices for writing good unit tests for components?
-
Dependency injection when using Redux - am I overthinking it?
Full post here but here's the main gyst.
-
Form elements in your design system - uncontrolled components are the way to go?
Full post is here.
-
What's best practice for managing state without Redux?
I recommend accessing your state via a hook..
-
Agnostic state and service management in React.
Here's a article written about service and state management. It's on github here if you want to submit PRs for it.
msw
-
Modern React testing, part 5: Playwright
We’re going to use Mock Service Worker (MSW) for mocking network requests in our integration tests and in the app during development.
-
Easier TypeScript API Testing with Vitest + MSW
However, I discovered a great combination that transformed my API call testing in TypeScript: Vitest and Mock Service Worker (MSW). Their well-crafted design makes them incredibly easy to use, enhancing the overall testing experience.
-
Creating mocks for testing react code
While mocks are effective, they require modifying the component's internal logic or mocking global functions like fetch. This can become cumbersome for complex components with numerous API interactions. Here's where MSW shines.
-
Storybook 8
> For those wondering what the use case is, you must not have tried it. It does take work to set up (with each version that's less), but it can be very nice to test in isolation esp in cases where a component is under a login, the 4th page of a 10 page form, etc. Also obviously if you're working on a component library that ships without an app, Storybook can be your development and/or demo app.
I have worked with storybook extensively over the past couple of years and my team is moving away from it in favour of MSW (https://mswjs.io).
For "4th page of a 10 page form" during the development there's hot reloading which is really stable nowadays and haven't failed me, although I understand that some setups are old and it might be easier to configure Storybook than good hot reloading.
I'm not entirely sure about the testing part of it and I'd be grateful if you could elaborate. I haven't felt the need for some special setup with SB because for unit tests, I can test a deeply nested component separately. For E2E tests, I usually test the whole form.
I agree on the component library part, this is probably the only use case where Storybook is 100% justified, but I'm unconvinced about the
Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.
-
I made "TypeScript Swagger Editor", new type of Swagger UI writing TypeScript code in the browser
similar with msw.js, but fully automated
-
Partial: how not to mock the whole world
they could be network mocks (use msw)
-
How to Automatically Consume RESTful APIs in Your Frontend
With orval, we can also integrate the API client in our unit tests. Orval provides first class support for mocking through the (Mock Service Worker)[https://mswjs.io/] library, and it can automatically generate the MSW handlers for testing server.
- Polly.js – Record, replay, and stub HTTP interactions
-
How to Successfully Integrate with Legacy APIs Using NodeJS
Consider a hypothetical scenario where data from a list of companies within an ERP needs to be retrieved. As a personal recommendation, leverage tools like MSW for top-level mocks, which can significantly enhance the testing process.
What are some alternatives?
redux - A JS library for predictable global state management
Nock - HTTP server mocking and expectations library for Node.js
zustand - 🐻 Bear necessities for state management in React
rtk-query - Data fetching and caching addon for Redux Toolkit
miragejs - A client-side server to build, test and share your JavaScript app
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
axios - Promise based HTTP client for the browser and node.js
json-server - Get a full fake REST API with zero coding in less than 30 seconds (seriously)
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
jest - Delightful JavaScript Testing.