Video

Hi Ryan! Maybe I'm wrong, but as I know NEXT_PUBLIC will be included in the client-side JavaScript bundle, making them accessible to anyone who can inspect the website's source code.

should firebase env vars be added to vercel platform to a prod app as NEXT_PUBLIC_...?

What a great video

some case this method can lead to undefined data value. cmiiw

How do you customise your layout depending on which child is active?

Nice

Great content with premium quality of video

How to properly implement layouts with pages that are completely different typically from the rest of your pages? For example, login/sign up page. Login page typically doesn’t have a nav bar for example (let these pages without the need for a navbar be set x), but all other pages in your web app for example would have the nav bar (set y). Would you hence have to nest pages/layouts for set y separately from set x, such that you have a separate parent layout for nested directories for set x, and another parent layout for nested directories for set y? This would allow you to import for example your navbar component only for set y. And You obviously wouldn’t want to just overlay the login page over the top with CSS since the DOM elements and info you are protecting would just show up in dev tools.

Great video. But I'm curious of why aren't you using portals and dialog element for the modal. Any particular reason?

Wonderful, thanks

To make it work I had to add makeRequest in post.js ``` const api = new GhostContentAPI({ url: process.env.GHOST_URL, key: process.env.GHOST_CONTENT_API_KEY, makeRequest: async ({ url, method, params, headers }) => { const apiUrl = new URL(url); Object.keys(params).map((key) => apiUrl.searchParams.set(key, params[key]) ); try { const response = await fetch(apiUrl.toString(), { method, headers }); const data = await response.json(); return { data }; } catch (error) { console.error(error); } }, version: "v5.0", }); ```

for Module Path Aliases you need to set baseUrl first "baseUrl": ".", "paths": { "@/*": ["./*"], "@/components/*": ["components/*"], "@/styles/*": ["styles/*"], "@/lib/*": ["lib/*"] }

How to send success/error toast from server actions? Do we need to return something from them and call the toast in the client component?

Hello. Thank you for the tutorial i really enjoyed! One question, is your server-actions folder considered Nextjs API? I am creating web based games that are going to be embedded on an Iframe on a nextjs project and deployed via vercel with a nextjs api that connects to supabase.

Awesome! Finally, someone who uses proper English!

Thanks so much bro I'm working on a fairly complex app with a lot of client side code I'm using react query for easy error handling and loading state too Should I switch to SSR or dynamically import components Cause the app is insanely slow and I'm very frustrated about it Thanks so much bruv 🙏

as a foreigner i dont underatand exactly . could u explain once more by comment?

thanks alot for videos

THANK YOU THANK YOU THANK YOU ... All my other tutorials are now obsolete ... geeeze

This is a really helpful compliment their docs. Thank you!!

If you have a src folder, try placing it in there. My middleware didn't run until I did that.

I prefer audio only, video is distracting. Some other youtuber shakes his head too much the entire video; great tutorial, great guy, but I cover the video popup because my head hurts with too much motion

Nice

Thank you so much I don't know if it's only for me but the documentation could not help me about this part

Will this make all the components client components?

Thanks for your opinion, i'm wondering if you still use The same structure.

Hi Ryan, I'm from cambodia

Really underrated channel. Thank you for the concise explanations

❤❤

awesome!!

“Your code looks like I wrote it”… they’ll know what I mean

Thank you so much!

Really helpful better than the HOC approach

AuthJS has probably the worst documentation I've seen. What's sad is that the reason the docs are bad is not because they don't have enough people or resources to write proper documentation, but because the creator is so opinionated that he refuses to write docs on any auth methods (credentials provider) that he "doesn't believe in" and thinks authJS should be reserved for "competent" and "senior" people that know the depths of auth (as if that will somehow help them understand authJS's custom abstractions) so that's his excuse for poor documentation.

No need for 3rd party auth...

will be really cool if _ suffix will work for layouts _myLayout/test.tsx (with layout) _myLayout/_test.tsx (without layout)

Great job explaining selectors! Thank you 🙏

nextauth is so frustrating to deal with ever since v5

Nice video! I would actually recommend doing everything in Typescript from now on, it's highly recommended

Amazing, Ryan🔥 Looking forward to the full-fledged app video🎉

Vercel needs phone number for 'verification' lol.

I am using page router. I guess it does not support colocation. Please let me know if I am wrong.

bro forgot to explain organizational Folder that doesn't affect routing

I've been struggling with this all day, what a lifesaver. Thank you!

You are just freakin awesome❤❤❤

thank you, mr. keanu reeves!!

Oh shit. I love how you teach and I'm surprised i'm not already subscribed.😢 I did hit that button.🎉

what was need of props driling in Todo.jsx? cant we use recoil state for that?

Subscribed

that was awesome and so easy to use