What its like to use NextJS in 2024

preview_player
Показать описание
Wanted to show off how I'm working with the new NextJS App router

my stuff
Рекомендации по теме
Комментарии
Автор

The “using bleeding edge tech to build cool shit” to “gymbro” pipeline is too real. I’m working on an AI app with Next 14 and RSC right now and have recently started going back to the gym seriously like a month ago hahah

ohLyln
Автор

Your content is really appreciated. Engagement on your videos will increase if you do SEO.

imtiazuddin
Автор

Server actions in client components did not work in vercel but were perfectly working in dev and local production build in 14.2. Hopefully it will work for you.

wervana
Автор

Cool vid and app. If you wanted to, a longer video on something like this, gen-ai+rsc, server actions + rq, would be very beneficial.

JohnCanCode
Автор

You don't need "server only" with "use server". The "use server" directive marks a door from client to server and will make sure that code stays on the server. like a REST endpoint. Under the hood, it basically gives the client a URL string to use for sending a request. There is no way to serialize a function across the wire, so server actions can only run on the server.

michaelfrieze
Автор

Recently started using supabase, i see you're using drizzle. Would you recommend using an ORM with supabase or just simply use the supabase cli to generate types?

I was looking at some of the starter project repos using supabase, and they generated the types with the supabase cli, it just seemed kind of scuffed. I dont know if anyone actually uses that workflow in prod.

Just curious your thoughts on it.

Dom-zyqy
Автор

Only issue is when you are a team working on a project the costs are too much especially for a developer from a 3rd world country. I have to pay 20$ per seat and the usage cost is another issue

rampandey
Автор

I'd like to request fullstack sveltekit - supabase.

gongshow