Question 1

How do I use ngrx-immer with NgRx ComponentStore?

Accepted Answer

Extend your store from `ImmerComponentStore` instead of `ComponentStore`, then use mutable syntax in updaters—for example, `state.movies.push(movie)` as shown in the README's `ImmerComponentStore` section.

Question 2

ngrx-immer vs manual immutable updates: which is better for performance?

Accepted Answer

ngrx-immer leverages Immer's structural sharing, which is efficient for deep updates but may add overhead for simple changes. In practice, the readability gains often outweigh minor performance costs in complex state trees.

Question 3

Can I mix ngrx-immer functions with regular NgRx reducers?

Accepted Answer

Yes, you can incrementally adopt it—for instance, use `immerOn` for complex mutations while keeping simple updates with standard `on`, as demonstrated in the README's `immerOn` example for NgRx store.

Question 4

What happens if I return state in an immerPatchState updater by mistake?

Accepted Answer

It will throw a runtime error, as highlighted in the README. Ensure updaters either mutate state without returning or return a new state immutably to avoid crashes.

Question 5

Is ngrx-immer compatible with the latest NgRx Signals?

Accepted Answer

Yes, it provides `immerPatchState` and `immerOn` specifically for NgRx Signals and SignalStore, enabling mutable syntax in signal-based state management, as detailed in the README.

Question 6

How to debug state mutations with ngrx-immer?

Accepted Answer

Use Immer's built-in debugging tools or enable strict mode, but note that the abstraction layer can make tracebacks less direct compared to manual immutable updates in NgRx.

ngrx-immer

What is ngrx-immer?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions