msw
jotai
msw | jotai | |
---|---|---|
150 | 107 | |
14,914 | 17,395 | |
1.9% | 2.0% | |
9.2 | 9.3 | |
4 days ago | 7 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
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.
jotai
-
React Server Components Example with Next.js
Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:
- 5 Alternatives to Redux for React State Management
-
jotai-wrapper, a super tiny and simple utility library
I've just published jotai-wrapper, a super tiny and simple utility library that makes using jotai even simpler. It comes from the necessity to migrate a project with react-context-slices to jotai. Both libraries share a similar API. While in react-context-slices you have the useSlice hook, in jotai you have the useAtom, useSetAtom, and useAtomValue hooks. In react-context-slices you define either React Context or Redux slices, while in jotai you define atoms. The need for the migration from the first to the second was a high memory usage by react-context-slices when using React Context slices.
-
React State Management in 2024
Atom-based: splits states into tiny pieces of data called atoms, which can be written to and read from using React hooks. In this group, we have Recoil and Jotai.
-
React Basics: Essential Knowledge for Every React Developer
jotai Is the signal based state manager I recommended, offering the best developer experience (in my opinion) as it eliminates the necessity to define and update a global store
-
π Dominate React Project Startups: Insider Tips for Dev Success! π€
Jotai π§ββοΈ
- Jotai β Primitive and flexible state management for React
-
Thoughts on Signals?
Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.
-
New Project: What is a good framework for a website?
Global State Machine: Jotai (great for any state that needs to be stored globally for your application)
- Is there a state management library, similar to Redux or Zustand, that automatically generates setters for the state you define?
What are some alternatives?
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
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
miragejs - A client-side server to build, test and share your JavaScript app
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
signals - Manage state with style in every framework
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
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]
axios - Promise based HTTP client for the browser and node.js
react-hook-form - π React Hooks for form state management and validation (Web + React Native)