Nerv vs unistore: What are the differences?

# Introduction:
When comparing Nerv and unistore, it is essential to understand the key differences between these two state management libraries in the React ecosystem.

1. **State Management Approach**: Nerv utilizes a more traditional approach to state management by utilizing class components with lifecycle methods. In contrast, unistore focuses on a functional approach using hooks for managing state in functional components.

2. **Library size**: Nerv is a lightweight library, ideal for projects where minimizing bundle size is a priority. On the other hand, unistore is a slightly larger library due to its feature-rich functionalities for state management.

3. **Immutability Handling**: Nerv does not have built-in immutability handling for state updates, requiring developers to manage immutability manually. In comparison, unistore provides built-in immutable state updates using helper functions such as `set` or `update`.

4. **Asynchronous Actions**: In Nerv, handling asynchronous actions requires additional libraries or custom solutions, as it lacks built-in support for asynchronous operations. On the contrary, unistore provides out-of-the-box support for handling asynchronous actions using middleware or async/await syntax.

5. **TypeScript Support**: While both Nerv and unistore are compatible with TypeScript, unistore offers better TypeScript support out of the box, providing type definitions and interfaces for seamless integration with TypeScript projects.

6. **Community and Ecosystem**: Nerv has a smaller community and ecosystem compared to unistore, which has a more extensive community support, active development, and a wider range of plugins and extensions available for additional functionalities.

In Summary, the key differences between Nerv and unistore lie in their state management approach, library size, immutability handling, asynchronous actions support, TypeScript compatibility, and community and ecosystem.