Content
@
0 reply
0 recast
0 reaction
Colin
@colin
these errors are the bane of my existence
6 replies
0 recast
31 reactions
henry
@henry
> delete bottom level component > error still there > delete one component up > error still there > delete one component up > error still there > delete one compo… > delete parent component > error still there > have a coffee > put back parent component and all children > error gone
1 reply
0 recast
0 reaction
rauchg
@rauchg
That’s unexpected given you’re on 14.2.1. Mind sharing more details? What turned out to be the underlying mismatch. Will make sure this gets fixed. Thanks for sharing.
1 reply
0 recast
0 reaction
timdaub
@timdaub.eth
I just run a regular ass express server on which I use JSX as a templating language and then I run a regular ass client where I just add the react root with document.querySelector() and react.createRoot and tbh beyond the initial boilerplate it is completely fine and performant. I cache for free on cloudflare
1 reply
0 recast
0 reaction
jtgi
@jtgi
Its depressing. Something about how useless the errors are and how difficult it is to debug. I wish it blew up the view in dev instead of rendering I always hit it well after i've introduced it. if you're using next.js, can try: https://github.com/BuilderIO/hydration-overlay sentry also has support for showing diffs.
1 reply
0 recast
0 reaction
Lazydev
@0xlelouch.eth
I gasped for a second thinking it was someone in my replies reporting this. what a mini heart attack XD 55 $degen
0 reply
0 recast
1 reaction
Bella_xx🎩
@juugyeth
I hate them so much, how do you deal?
0 reply
0 recast
0 reaction
mrtrosen 🎩
@mrtrosen
I have yet to have any desire to use react, and I doubt I will ever be convinced to... guess I'm still too old school for these fancy frameworks :)
0 reply
0 recast
0 reaction
taofeek.eth
@taofeek
Are you presently encountering this?
0 reply
0 recast
0 reaction
