Debugging in React/Redux a lot harder than when using Vue/Nuxt?

Am I the only one that feels kinda lost trying to debug things in Redux?

Maybe I got spoiled with Nuxt, maybe I need different browser tools, maybe I need to take a redux/reselect course to remind myself wtf is going on over here...

but I feel like even simple things like seeing a components props or the app state is difficult to do in browser inspector, even with the usual react browser extension.

I don't know what I'm hoping for here ... maybe a youtube video recommendation or a browser extension or a tiny violin. Either way this seemed like the best community on Lemmy to ask.

load all comments

keef 1 point 3 years ago

Are you using the extension for redux debugging as well? I know you mentioned the usual react extension but just mentioning it in case.

https://github.com/reduxjs/redux-devtools

save

path: 0 655801, hotness: undefined, score: 1, children: 3

WheeGeetheCat 2 points 3 years ago

This didn't work 'out of the box' for me so I bounced off it. Sounds like its worth another look. I'll dig into it today. Thank you!

save

path: 0 655801 656164, hotness: undefined, score: 2, children: 2

keef 2 points 3 years ago

Hopefully it helps you 🥰

If the code base you are working with dumps a ton of shit into the redux state it might need to be sanitized. I implemented this at my last role and it actually redeemed the dev tools tab to being useable rather then just crashing

I would also mention Redux has kinda fallen out of fashion for some other choices now. I personally use Zustand/Jotai but the move to redux tool kit can be an easier step if it’s an option

save

path: 0 655801 656164 656375, hotness: undefined, score: 2, children: 1