What its like to use NextJS in 2024
HTML-код
- Опубликовано: 24 апр 2024
- Wanted to show off how I'm working with the new NextJS App router
Codebase: github.com/Davis-Media/weight...
my stuff
discord: / discord
x (twitter): / bmdavis419
insiderviz: www.insiderviz.com
blok: www.theblokapp.com 
Наука
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
This is the perfect summary of what I want to be. Gym bro who uses bleeding edge tech to build cool shit
@@bmdavis419I vibe with that. I’m building a SaaS product in SvelteKit right now because I’m too sore to move from leg day on Friday 🤣
Your content is really appreciated. Engagement on your videos will increase if you do SEO.
great video . keep it up. thanks
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.
I've got it in prod rn and its working fine for me...
They would definitely work in Next 14. I would double check the docs if it didn’t work for you
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.
Yea I will for sure at some point, there is a ton of important stuff there that definitely deserves a big tutorial
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.
Yea I always just use drizzle and connect directly to the DB. Will have a full tutorial in the next few days
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.
Not only that, but you should be able to import server actions in client components (when needed), which server-only should prevent.
@@JohnCanCode I am not sure if "server only" would prevent importing a server action into a client component. The function itself is not being imported into the client, instead, the client just gets a URL string, so maybe "server only" still works.
Interesting. I agree, I’ll have to test it
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
I'd like to request fullstack sveltekit - supabase.
Planning to record tmrw!