Member-only story
Does your next project need Flux (Redux, Vuex, Mobx…) or not?
It is so frustrating when you are introducing new technology to your project and to your team, is it because this technology is new, famous, trendy, magical and everybody is talking about it? However, you are not really sure if you are going to need it or not.
Think about this situation, do you really need all the things you are using in your project? Maybe yes, maybe no and probably if you go to your ‘package.json’ you will find a package that you do not remember what exactly it does!
In this article, I want to talk to you about a few things that I have learned from working with Flux (Redux, Vuex, Mobx…) on real different projects.
But before, if you are not aware of what I am talking about, I recommend that you read some articles like: “A cartoon guide to flux” where you can learn about ‘the first’ pattern of the group. And after Flux, some other patterns were born like Redux, Vuex or Mobx among others.
Some problems that I have found learning Flux
Working with these technologies in projects like Smarthotel 360 public site (React + Redux + TypeScript) or PWA Builder (Vue + Vuex + Nuxt + TypeScript) and some boilerplates that we are creating related to Vue or Nuxt, we have found some problems, let me introduce them to you.
