JavaScript

2460 readers

1 users here now

founded 2 years ago

MODERATORS

erlingur@programming.dev

Ategon@programming.dev

nick@programming.dev

Debugging in React/Redux a lot harder than when using Vue/Nuxt? (sh.itjust.works)

submitted 2 years ago by WheeGeetheCat@sh.itjust.works to c/javascript@programming.dev

4 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] WheeGeetheCat@sh.itjust.works 2 points 2 years ago (1 children)

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!

[–] keef@programming.dev 2 points 2 years ago (1 children)

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

[–] WheeGeetheCat@sh.itjust.works 2 points 2 years ago

its enterprise company code so it's definitely older as far as tooling. No typescript yet, etc.

If I dont have any luck with the redux tools I'll look into sanitizing the redux state. Thanks for the tip!