Why another state management framework for Angular?

Austin
Austin
Mar 17, 2018 · 4 min read
Image for post
Image for post

I didn’t set out to make my own state management system just for fun. I actually spent a lot of time trying to avoid creating my own. I created a library called ngrx-actions wraps NgRX to try to solve some of my pain points but in the end this just felt like a hack and I was always going to be making decisions on this new library based on the architecture of NgRX. In the end, I created a new state management system called NGXS which took many of the concepts of Redux but reimagined them for Angular.

So what were the gaps that I found and wanted to approach differently with this library?

Redux was designed for React

Switch Statements

Its more Angular-like code style

Dependency Injection

Boilerplate Hell

Effects can be painful

Listening to Dispatched Actions

Promises

Check it out!

Image for post
Image for post

Thanks!

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store