This video will review the latest updates in the NextJs 14.2 release. 👉🏼 New courses → www.hamedbahram.io/courses 👉🏼 Work with me → www.hamedbahram.io/hire
We can't use turbo, it's not production ready!!!!, it happens a lot with nextjs, if a feature is not production ready or if only works in vercel, for me it's makes no sense to use it.
That's totally fine! However, I have a slightly different take, releasing features before they are ready helps making them better by community feedback, also it allows me to know what's coming down the line.
I don't know if it was caused by the new version of Next.js because I just encountered an issue where the updating of pages in the browser is not real-time (npm run dev). Every change I make requires me to restart npm run dev to see the updates. Am I the only one experiencing this issue?
@@hamedbahram currently I'm having trouble setting up a project idea using Twilio and Whisper for real time transcriptions on a phone call. Use cases where you need to fetch something on the server and pass it to a client component, and have that client component initialize a device without rerendering and invalidating the device with the cleanup function are tricky to manage in Next, not to mention handling the websocket from the frontend...bit of a complex project, maybe not ideal for a video but I'd like to see a tutorial that handles cases that involve complex client => server => client workflows where you absolutely have to use both client and server components and have them mesh well
I have been having the problem of "React Context is unavailable in server components" error I have tried everything possible but to no avail...any suggestions pls😢?
seems like you're trying to use React context inside server components. You need to use a client component for that, you can add the `use client` directive on the first line of your component file.
@@hamedbahram Thanks for your response but I am using nextjs and I wrapped my Root layout with the useSession, so that I can use the session in my signin page but it throws the error whenever I try to start the development server
We can't use turbo, it's not production ready!!!!, it happens a lot with nextjs, if a feature is not production ready or if only works in vercel, for me it's makes no sense to use it.
That's totally fine! However, I have a slightly different take, releasing features before they are ready helps making them better by community feedback, also it allows me to know what's coming down the line.
I don't know if it was caused by the new version of Next.js because I just encountered an issue where the updating of pages in the browser is not real-time (npm run dev). Every change I make requires me to restart npm run dev to see the updates. Am I the only one experiencing this issue?
It may have been! update to 14.2.2 and see if that resolves the problem.
Great video Hamed! Been enjoying your Next.js and collab videos a lot lately, keep it up!
Thanks, Delba! I appreciate that. I'd love to have you on for a chat... You've inspired me so much 🌷
Hey Hamed, awesome video! Would love to see some tutorials on using Twilio Conversations with Next.js!
Thanks! Great suggestions, can you expand on what specifically you like to see using Twillio?
@@hamedbahram currently I'm having trouble setting up a project idea using Twilio and Whisper for real time transcriptions on a phone call. Use cases where you need to fetch something on the server and pass it to a client component, and have that client component initialize a device without rerendering and invalidating the device with the cleanup function are tricky to manage in Next, not to mention handling the websocket from the frontend...bit of a complex project, maybe not ideal for a video but I'd like to see a tutorial that handles cases that involve complex client => server => client workflows where you absolutely have to use both client and server components and have them mesh well
@@hamedbahram Sure! I’d like to see how you would make a real-time chat application.
@@ledoublez Fantastic!
@@PraiseYeezus I like the idea! I'll definitely have a video on websocket in NextJs, so hopefully that'll help.
Very Kind !
Thank you!
I have been having the problem of "React Context is unavailable in server components" error I have tried everything possible but to no avail...any suggestions pls😢?
seems like you're trying to use React context inside server components. You need to use a client component for that, you can add the `use client` directive on the first line of your component file.
@@hamedbahram Thanks for your response but I am using nextjs and I wrapped my Root layout with the useSession, so that I can use the session in my signin page but it throws the error whenever I try to start the development server
please make a video what you wana use turbo pack and what are the advantages in production when its available ..
For sure! I have that in mind.
thanks hamed ❤
My pleasure!
always thanks!!!
I appreciate that!
I really hope the new hydration error messages are more detailed
Absolutely 😅
Cool video. I heard Next.js 14.2 is broken though.
Thanks! It's working all fine on my end 🙂
Everything is broken in some way when released. Next 14.2 is fine, relatively speaking.
@@codefinity I've run into some issue in one my client projects. Investigating to see what's going on...
@@hamedbahram 👍 there’s always SOMETHING.
❤❤👆🌽
🙏🏼
By this time, I have completely given up on Next JS
That's alright. What's your preferred framework?