For the last few months I was working with Nuxt to rebuild the web application written with Express and Vue. The idea was to have both server and client-side rendering handled in the one place by the same framework. And since the frontend was already written in Vue, naturally Nuxt was a framework that I chose (for applications written in React I suggest to take a look at Next).
Nuxt is a relatively new library, so sometimes the lacking of documentation and resources might be really frustrating. …
I was working with React for the last few years, first separately, then together with Redux and other libraries from the React-universe (react-router, react-redux, prop-types, etc.). I liked how simple and convenient it was and my experience with React was always a pleasant one. I am happy to live in times when we have lots of great tools to help us develop applications better and faster.
As it states in the Bunny Theory of Code, the code tends to multiply in a quick way. And even with such great tools as Vue and Vuex it’s easy to make a mistake that might grow later all over the project. Here I will talk about Vuex and its getters, and how they might be used in a wrong way. And while dealing with that, I tried to figure out what Vuex getters are good for and how they work under the hood.
Software Engineer at unu GmbH.