"there is no reason to for me to recode this" Yes you have a reason. To actually demonstrate the first steps of putting together stuff. If you actually start with following the documentation, put together first components and pages, you would have met the same bugs and wrong explanations anyone meets when trying to put this together. Instead you were scrolling on a ready app which is not familiar for the viewers. It was easier and faster for you but did not support the purpose of this video. Still, thanks for your effort. Finally I ended up not using this library. It turned out that there are too much errors that it makes zero sense to me to invest energy in it. There are component libraries which have decent docs and less bugs. I don't even understand why people talk about shadcn as a gamechanger. It is not. Please do not hype stuff just for fun.
you're not being transparent with us you have an error, and it's because of shadcn the code you copied without really going over it, includes RadixUI DropdownMenu.Portal component, which is a React Portal, if you don't give that one the ref/element to "teleport" to, it will use document.body, and when it does that it will complain that your framework doesn't recognize the code it's supposed to hydrate..., so you can't just simply copy paste it same with other components that use Portal P.S no audio crackling/popping in this one 👍😁
@@brettwestwooddeveloper 1. the previous video I commented has terrible audio because it is popping and crackling, and me writing about it got you mad? 2. you created a video about something and noticed an error and hit publish without mentioning it, and me writing about it + explaining the reason why it happened made you mad? I subscribed, I still feel no ill will towards you. Was it ego, bad day, whatever it was, probably work on it? gl
1. definitely no audio or crackling in that video and 2. you can literally copy and paste the code and not have errors like you say. This is my last message to you. You are probably just surprised I responded since you are a keyboard warrior@@wasd3108
@@brettwestwooddeveloper well, you have an error. It's not from dropdown cuz it's only exporting the imported Portal comp, but if you copy paste Dialog (which is probably the Modal you have that's causing you trouble?), literally new project, copy paste Dialog, error. Remove the Portal and it will fix errors. A component manipulating the dom unexpectedly like that won't work with SSR. Yes, I was wrong, I apologize for that, it wasn't that particular dropdown code you showed that caused the error, I saw portal imported and didn't check if it was used or not. But other components like Dialog uses it and it will cause an instant error anywhere in NextJS. Here's visual proof for audio being bricked: this is a slug for imgur image "lpdenqQ" I hear popping and crackling very rarely in content, but here it is, so I used Audacity and inspected the spots I hear popping (I hear it clearly in speakers and on my headphones), I am not very informed on audio so I can't tell you what creates those, but they're all over the place and every spot I zoomed into had such jagged line. Also your home page introductory vid has them. Why would I be surprised you responded if you already responded twice...
![ทุกครั้งที่หลับตา (Lucid Dream) - AYLA's [ Official MV ]](http://i.ytimg.com/vi/4i1OBAQyv58/mqdefault.jpg)
Just what I needed.
Thanks 🤗
You are welcome!
Thanks for making this.
My pleasure!
Great job 🎉
Thank you!
you're awesome 💙
Thank you!
"there is no reason to for me to recode this"
Yes you have a reason. To actually demonstrate the first steps of putting together stuff. If you actually start with following the documentation, put together first components and pages, you would have met the same bugs and wrong explanations anyone meets when trying to put this together. Instead you were scrolling on a ready app which is not familiar for the viewers. It was easier and faster for you but did not support the purpose of this video.
Still, thanks for your effort.
Finally I ended up not using this library. It turned out that there are too much errors that it makes zero sense to me to invest energy in it. There are component libraries which have decent docs and less bugs. I don't even understand why people talk about shadcn as a gamechanger. It is not. Please do not hype stuff just for fun.
GFY 😁
Shad is the best, way better than the rest like flow-bite, skeleton etc.
@@brettwestwooddeveloper No, not really.
Anyway, I will try again now, maybe they fixed the documentation and the flow is smooth.
you're not being transparent with us
you have an error, and it's because of shadcn
the code you copied without really going over it, includes RadixUI DropdownMenu.Portal component, which is a React Portal, if you don't give that one the ref/element to "teleport" to, it will use document.body, and when it does that it will complain that your framework doesn't recognize the code it's supposed to hydrate..., so you can't just simply copy paste it
same with other components that use Portal
P.S no audio crackling/popping in this one 👍😁
Damn you must be a fan and a loser lol
@@brettwestwooddeveloper
1. the previous video I commented has terrible audio because it is popping and crackling, and me writing about it got you mad?
2. you created a video about something and noticed an error and hit publish without mentioning it, and me writing about it + explaining the reason why it happened made you mad?
I subscribed, I still feel no ill will towards you. Was it ego, bad day, whatever it was, probably work on it? gl
1. definitely no audio or crackling in that video and 2. you can literally copy and paste the code and not have errors like you say. This is my last message to you. You are probably just surprised I responded since you are a keyboard warrior@@wasd3108
@@brettwestwooddeveloper well, you have an error. It's not from dropdown cuz it's only exporting the imported Portal comp, but if you copy paste Dialog (which is probably the Modal you have that's causing you trouble?), literally new project, copy paste Dialog, error. Remove the Portal and it will fix errors. A component manipulating the dom unexpectedly like that won't work with SSR.
Yes, I was wrong, I apologize for that, it wasn't that particular dropdown code you showed that caused the error, I saw portal imported and didn't check if it was used or not. But other components like Dialog uses it and it will cause an instant error anywhere in NextJS.
Here's visual proof for audio being bricked: this is a slug for imgur image "lpdenqQ"
I hear popping and crackling very rarely in content, but here it is, so I used Audacity and inspected the spots I hear popping (I hear it clearly in speakers and on my headphones), I am not very informed on audio so I can't tell you what creates those, but they're all over the place and every spot I zoomed into had such jagged line. Also your home page introductory vid has them.
Why would I be surprised you responded if you already responded twice...