Are you having trouble trying to debug react rerenders? Debugging unwanted react rerenders can be one of the most frustrating and tricky problems when building Reacts apps. Especially when working with large systems, trying to identify which prop or hook changes are triggering a re-render can be enough to drive anybody mad.
So you’re probably aware that you might not need Redux, but maybe Redux is a good fit for your app. That means we should use it for managing all of our application state… right? Wrong.
JQuery is quickly becoming a thing of the past, and in it’s place stands React. I mean, even John Resig, author of JQuery, uses React now. So how can you refactor your website to use React instead of JQuery?
.When I first started out using Redux, I learned very quickly how to use (read: abuse) Redux actions. Actions and middleware used to be simple: if it’s synchronous, put it in an action, but if it’s asynchronous then you should use middleware.
One problem I’ve been struggling with lately is: what is the best way to store tokens when using redux? I could store it in the Redux state, but then it wouldn’t be there after refresh. I could just store it in the browser’s localStorage, but where would I do that?
This post is part of a series of mine on building web applications from the ground up. It covers everything you need to know to completely finish a web application. If you haven’t been following the series, please go back and read part 1.
So you want to build a web app. Well, what’s stopping you? If you’re reading this, you’ve probably already been programming for some time, but you’re just missing some of the steps. I’ve been there before. I know how frustrating it can be to know 70% of what you need to do to build a killer web app for an idea you have, but not have enough knowledge to take the idea from beginning to end.
