How to get rid of this shit ?
Unanswered
Grand Anglo-Français Blanc et Or… posted this in #help-forum
Grand Anglo-Français Blanc et OrangeOP
Fucking annoying message
11 Replies
@Grand Anglo-Français Blanc et Orange Fucking annoying message
well... fix it 🤷♂️
Check your server console to see which code bracket it comes from and then check why it causes an hydration error. Then fix the hydration error
Check your server console to see which code bracket it comes from and then check why it causes an hydration error. Then fix the hydration error
Sloth bear
Fix it by dumping Next.js. It sucks. It solves problems that are applicable to a minority of the usecases. The whole SSR / client side hydration thing is unnecessary in most cases and just adds complexity
@Sloth bear Fix it by dumping Next.js. It sucks. It solves problems that are applicable to a minority of the usecases. The whole SSR / client side hydration thing is unnecessary in most cases and just adds complexity
Sun bear
Freely do so if it does not align with your use case, but nextjs is the most popular framework for a reason. The issue you are seeing is a valid one.
Only thing I would add is for the error message to be more exact where the problem occurs / what node is different on server. I could understand your frustration there.
Only thing I would add is for the error message to be more exact where the problem occurs / what node is different on server. I could understand your frustration there.
Sun bear
well that settles that :D
Egyptian Mau
i just had this and in my case it was because i put
I know there are probably dozens of other possibilities why you could run into this error, but hey, you never know, right?
method="post" on a form element with an action defined. As soon as I removed that attribute, the hydration error went away.I know there are probably dozens of other possibilities why you could run into this error, but hey, you never know, right?
tanstack is mogging nextjs to be honest
@Longtail tuna tanstack is mogging nextjs to be honest
Sun bear
Haven't gotten around to trying tanstack out yet, but if something is popular generally it's because it's good.
@Sun bear Freely do so if it does not align with your use case, but nextjs is the most popular framework for a reason. The issue you are seeing is a valid one.
Only thing I would add is for the error message to be more exact where the problem occurs / what node is different on server. I could understand your frustration there.
Sloth bear
And if you ask me, it seems like a lot of the projects and popularity comes from students who create their first hello world app like this: https://discord.com/channels/752553802359505017/1463214936749637662/1463214936749637662
@Sun bear Haven't gotten around to trying tanstack out yet, but if something is popular generally it's because it's good.
Longtail tuna
nah, it;s because they were first to implement rsc