Something's really off..
Answered
6vz posted this in #help-forum
6vzOP
So... I get this error about using await/async. It is caused by
The best part? I was doing EXACTLY SAME THING 1 week ago, and it was working without any notices, but now, it just stopped.
Can please someone help me with my issue? I can share code that causes this error, on request.
node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js . This happens after using useState() and TextField with [MUI](https://mui.com).The best part? I was doing EXACTLY SAME THING 1 week ago, and it was working without any notices, but now, it just stopped.
Can please someone help me with my issue? I can share code that causes this error, on request.
36 Replies
6vzOP
NOTE: I DO NOT HAVE ANY ASYNC IN MY CODE!
You cant use useState() inside of a server component? Share your code if you want assistance.
No problem.
So what you have shown me here looks fine. Can you provide me with the stack trace for the error your getting?
6vzOP
Let me boot it up.
also if you do 3 backticks then type 'js' then go to next line and put your code itll do proper syntax highlighting just a tip 🙂
6vzOP
const you = 'abc123'6vzOP
I know, but since Discord converts longer messages to files, there was nothing i could do
Can you give me the error from the console instead of the screenshot here?
Ahhhhh, I gotcha
6vzOP
This error for some reason does not appear in console.
Hmmm, okay. interesting.
Remove your navbar client from the code.
Answer
Nope, not when troubleshooting, just wanted to makesure your not.
6vzOP
Let's just say that.
6vzOP
it works
Glad to help!
Was it the navbar?
6vzOP
yeah, i was having async in the navbar
tho it should say at least something that it was in the navbar
Ye heheh. stack trace leaves something to be desired for sure.
6vzOP
Thank you for helping me out with it
Weird it didnt appear on the console, ussually it appears both client side and server side. Anyways, GL!