thankyooooooooooouuuuuuuuuuuuuuuuuuu soo muchhhhhhhhhhhhhh i was having an problem like i couldnt get my data to display everytime i deleted or added it, but while watching this video, i got to know about revalidatePath and it solved it like thankssss a lottttttttttttt~

Max said end of React. You say end of Remix. Whom should I listen to?

I'm so grateful I found this video

Awesome demo and explanation of the generative UI in AI applications! It's fascinating to see how interfaces can dynamically interact with users based on their inquiries. I use Plerdy's free version to optimize user experience by analyzing how visitors interact with my site, which helps me make similar user-centric decisions without sophisticated AI tools. It’s amazing to see how technology continues to evolve in this space! 🌐

Amazing video. This was so helpful! Thank you so much.

Amazing 🔥🔥

Great tutorial! Note: The use of the word "essentially" (84 times) was perhaps a little overused 🙂

Dude I believe there’s some issue with the sound tho

this is absolutely AMAZING ! thank you so much! just amazing !

Vercel AI

great stuff ..would love that tutorial

Great work! Would really love a tutorial with the SDK.

thanks a lot! I've subscribed!

Hi there, great tutrial so far, love the explanations I had a questions around the 21:50 where you are signing up, I a getting a { status: 429, code: 'over_email_send_rate_limit'} error from supabase, I didnt change the code, just downloaded the repo and was following along, are you aware of why this could be?

The blog says quite clearly that remix is not going to disappear, just rebranded as react router v7. And it also hints at server components coming soon. It would be really weird if remix were to just disappear all of a sudden given that Shopify created, maintains and uses it.

I've taken a similar approach. The only thing that I am not a big fan of is calling getUser() for the post requests requests. It slows down the app a little bit, but it's way more secure tho. I wonder if there's some work-around for that.

Great work. Can you please add the appropriate license file to the git repo in case you want this code to be shareable with others like me.

Didn't see that coming, remix taking a "little nap", I think for any serious projects you should stick with nextjs, seriously.

Wow this is a rip-off of this exact same video (even the shirts are the same): kzbin.info/www/bejne/q5zTmKt7mtKLqc0si=oyd_mdqTwIi03UY9

that's another reason to love Svelte : their fullstack offering Sveltekit is built by themselves

I now using the router from the react-query devs in my Vite apps. The react-router broke my projects too many times

EDIT: Since filming this they have updated the blog post, to try clear up some confusion about where the Remix brand is going: remix.run/blog/merging-remix-and-react-router Have you used React Router or Remix? What do you think of this move? More confusion in the short-term? Less in the long-term? Let me know!

revalidatePath thing made me rethink using NextJS again, I really like Remix.

bro, this is a quality tutorial. thanks!

Overall Great Awesome Work You Did There!!! I am not 100% sure about the things I will write in this comment. But I guess it is better to check out and learn. Only thing that conserns me is that on 1:31:45 you've added notFound() from next/navigation. Actually because you are using generateStaticParams that notFound fn would only work in local environment but not at production level. Let me explain why? generateStaticParams runs before the corresponding Pages or Layouts are generated on next.js build time. What is happening behind the curtain: Using generateStaticParams on a path that is SSR, the build works because it could access the data but then the pages never got created on the build time. This means, your pages are built anticipating static rendering but at runtime. So when anyone tries to go to the path, there's no static page to render and also usage of dynamic functions are not allowed in Next.js (in this case it is the searchParams) - so you will get the 500 error on production. I may be 100% wrong about this because of this new server and client directives actually a huge mess to grasp. We're using a mix of static and SSR which is why I may got mixed up. Here are some references that made me question your approach. Static & Dynamic Rendering: nextjs.org/docs/app/building-your-application/rendering/server-components#static-rendering-default Dynamic Functions: nextjs.org/docs/app/building-your-application/rendering/server-components#dynamic-functions

Hi there, fantastic video, really love the way you explain things are you able to do a breakdown on how you created the JollyUI? would love to learn more about the architecture and creating reusable components for design systems

any framework!... for react :(

Part of me is smiling watching this, it's also something interesting to build in the learning process

Nice! The problem with all F1 related apps is the violation of their IP... It is literally impossible for you to do anything.... Even the telemetry data is registered... it can't be used without their permission. BTW, Lewis is Ok... ;)

This was my first time trying something new here, I appreciate it wont be perfect, but that is quite fitting with the conclusion of the video! Let me know what you think, and did you pick up on who I may support in F1?... Subtle.

How to break apart sprite sheets?

queeestion? can you also check in middleware for different subscription tiers? eg. there are three groups of posts (posts and info to which group they belong is fetched from cms) thanks!

fantastic video! was looking for an example of rendering markdown with nextjs. glad i stumbled across this

good stuff!

i think this works as well i am not sure though ^react(/(.*)$|$)

VS Code What font do you use?

"Any tech stack" , what about react native?

Honestly I found It difficult to Undestand the tutorial I will continue after learning further Thanks

Excellent breakdown and code. Not many out there yet for this fantastic new package.

I rarely comment on youtube videos, but you are going to blow up. The production quality is amazing, and you are very good at explaining content!

thanks for creating this great video, but may i ask in ImageResponse i cant use reactElement it says cannot find name div or any other html tag, is it deprecated ?

the sound is wau too low. i thought my headset were broken

Thanks for this video.

You're doing a great job! This is a great video, thanks for creating it.

Hey james please make more longform stuff.

This is the best straight to the point supabase nextjs tutorial, I only have one question is how can we customize the sign up page to get more information about the user! also manage user permissions and roles like pro and free members of a certain app. Thank you for your efforts!

Subscribed :D

For the constant index accesses, it seems very helpful, but will that really be okay? Sure the regular indexing won't cause any side effects, but proxies exist! It'd be severe abuse of notation, but theoretically `proxy[key]` needn't return the same value, or even the same type of value both times, right? Will TypeScript be able to understand this, or will we be able to tell it that explicitly somehow? Or is this just broken with no fix?

Thank you for this great video!

Like i have: restaurants/xyz. Where xyz is the restaurant and i need to fetch the details of the specific restaurant. What to do in this case ?