Next.js Server Actions... 5 awesome things you can do
A full tutorial and breakdown of the new Next.js Server Actions feature. Learn how to handle form submissions and implement optimistic updates without the need to API routes.
#reactjs #javascript #webdevelopment
Get the Full Next.js Course fireship.io/courses/nextjs
Server Actions Announcement nextjs.org/blog/next-13-4
Пікірлер: 392
If you like this style of content, check out the full course for more. Use NEXT30 to get 30% off (expires this sunday) fireship.io/courses/nextjs
@toastrecon
Жыл бұрын
Purchased! Can't wait to get started.
@abdullahrafique2883
Жыл бұрын
Is this nextjs course with latest updates? Like next13
@mgams4830
Жыл бұрын
like the miniature of the video
@maxwebstudio
Жыл бұрын
Take my money 💸
@Alcaatraz01
Жыл бұрын
Any chance Nuxt3 course happens? And/or sveltekit. Good stuff though.
Like how you specifically chosen dogs for this tutorial so you could have upDog as a function. Well played
@invinciblemode
Жыл бұрын
What’s updog
@funkenjoyer
Жыл бұрын
@@invinciblemode not much, sup?
InertiaJS also reloads components without needing to build an API, while also preserving state without a refresh, all from your backend router from ROR or Laravel. I don't like having server and client code in the same file, but that's just me.
Fantastic content. Information rich with no filler but seasoned with a little levity and entertainment. Perfect.
thank you, I finally started to understand developing technics thanks to your videos
I would love to see a video with frameworks and languages portrait as tribes and nations that fight over the Web like it was an history class
Amazing video. Thank you ! So excited about those updates 🔥
“Javascript rules them all” idea has been a smart choice to handle both frontend and backend by a single language. server actions brings the same react conventions rather than nodejs or api routes paradigm and makes to adopt this approach easier. But I don’t know if it’s good or bad news for frontend devs since we all are becoming full stack devs gracefully like the old days (php+jquery). Nowadays having smaller teams is becoming a trend even for big companies after all.
@heroe1486
Жыл бұрын
It's not a smart choice, it would have been if the node ecosystem wasn't a mess and if there were better frameworks for it, a lot of people thus don't want to write their backend code in JavaScript and that's understandable. (Big) Companies would never use NextJS for the backend of a serious and not very small application.
@mertdr
Жыл бұрын
@@heroe1486 The reason I think it’s smart is that you can make a website without php but you cannot make a website without javascript. Of course I refer to today’s standards and php can be replaced with any other language in this context. I’m also not a huge fan of node and don’t enjoy backend scripting that much. But apparently things are going to evolve around this approach.
@IvanRandomDude
Жыл бұрын
Full stack is indeed a future. Businesses will not be paying specialists anymore, they will expect us to be able to deliver apps from UX to deployment. But that obviously has it''s cons. Knowing a little bit of everything means we will not be excelling in anything which can lead to overall lesser quality. Of course, talking about simple to medium projects. Big and complex projects with uber business logic will always require specialists and domain experts.
@oscarljimenez5717
Жыл бұрын
When tooling being upgrading year after year, frameworks, ai, etc. Frontend developers will convert to Fullstack developers, and Backend developers only be necessary in a microservice arquitcture or big apps, no need in small apps.
@oscarljimenez5717
Жыл бұрын
@@timebroua that's why backend developers will be not removed. Frontend developers will transition to fullstack and backend developers will be needed to be more expert. As backend developer, you really want to create the endpoints for a frontend developer? and then argue with him because comuncation problems?
Love your humour dude, thanks for the content! 😊
Server Actions are the feature I literally needed the most right now, I had two github-discussions running which where closed now because of this.
This is going completely over my head lol, probably because i dont have a concept of how this was done originally.
@user-sw2xg9lz6p
Жыл бұрын
+1
@heroe1486
Жыл бұрын
Remember we were all using Next because "it's just React but with extra goodness (file based routing, handy utility functions, middleware etc)"
@Gogonel290
Жыл бұрын
I feel like using react query its more easier, readable and intuitive, and can be used outside of html forms
@heroe1486
Жыл бұрын
@@Gogonel290 All of that without needing to couple your backend code with your frontend one and not being forced to use Node, React Query makes everything very easy. And as a bonus it also works with Vue Svelte and Solid
@MasayaShida
Жыл бұрын
Same
Using server actions defined somewhere in client components even with having to use useTransition is still really cool and probably going to be my most used feature.
@gin2064
Жыл бұрын
same
@alulaleak
5 ай бұрын
when using a server action in a client component, does the action still happen on the server side?
@edan626
5 ай бұрын
yes@@alulaleak
Great video! Loves your coding tutorials!
You're a machine! Enjoyed the video.
Very clear you explanation, you're awesome bro
Thanks. best tutorial video ever seen.
I knew it was coming, I was prepared for the punchline, it still got me. Every. time. Curse you upDog!
I’m thinking that NextJS is turning into Ruby on Rails, which most people didn’t like because of how “magicky” it felt. In the other hand, if you understood how it works, then using RoR offered a big advantage.
@okage_
Жыл бұрын
agreed
@_sevelin
Жыл бұрын
I think next is unnecessarily more complex in terms of syntax. Doesnt seem that scalable now... Ror on the other hand is easy to understand...
@timalk2097
Жыл бұрын
I see now why most of the elder devs that were really successful were RoR devs (in my region at least)
@marusdod3685
11 ай бұрын
@@_sevelin you're talking about scalability, almost all companies that used ruby on rails migrated away from it because it was dogshit slow
@_sevelin
11 ай бұрын
@@marusdod3685 i meant the code's scalability (i think the better word would be maintainability). i can't imagine writing so much non relevant code to achieve something simple. at least that's where ror shines...
loved the timing with the like button glow up!
Awesome explanation, thank you
This update is so crazy good🙌🏻
Did you not apply any custom font here because it causes jitter in the UI when you revalidate the page?
Could you please describe more about database usage in actions? Because it is a more tricky thing, when you need to open a connection, then close it, or even open one connection over all actions ?:) I use surrealdb + server actions, and there are some interesting things with open and close connection :)
I love php working style happy to see nextJS mixing it with javascript.
I like SvelteKit approach more: it's quite similar but you still maintaining separation of execution concern (BE/FE).
I don't know, part of me really liked having react apps be frontend, and the ability to have something entirely different as my backend. I know i'm not being forced into this, but I kind of like the systems that we have now more than this. Will need to play with it more.
@kodekorp2064
6 ай бұрын
Its similar to developing in Ruby On Rails framework.
2:06 Interesting. I usually put the server-side data into a state so I can update it immediately from the response I get back from the server
The AI Audio is pretty good in this one.
@yellowboat8773
Жыл бұрын
Dam I didn’t even realise this was AI generated voice?
@supremebeme
Жыл бұрын
@@yellowboat8773 yeah it’s especially funny during the jokes because AI can’t get the cadence quite right.
@MrFrozener
11 ай бұрын
for non-native english speakers, it's far too fast
Nice one. Loved it
fantastic content
NextJs server actions looks like aspnet postback update panels from 2000. Seems to work the same way. It even posted back via ajax and didn't do a full page refresh. What is new is old.
@migue018
Жыл бұрын
Yeah and it worked like a charm...no page reload!
Geez this stuff is cool!
This was great, tnx!
That whats up dog killed me
Damn. First time I’m seriously considering the pro membership.
Can you please make a short video on how to upload the image using this server actions from client component to server component to get that image URL.. Please make video I am very struggling with it.
Fact : I learned everything I need from this vid
Do you know what’s great about api endpoints? Freedom to move your app to a different backend
@ianbdb7686
Жыл бұрын
exactly
@chipmo
Жыл бұрын
In practice "move your app to a different backend" will almost certainly involve a lot more than simply changing a url. Many frontends are typically strongly coupled to a particular backend and vice versa with the backend only existing for that frontend, and the argument is that in many cases having additional abstraction around this coupling can make us less flexible rather than more. React has always been bullish on removing barriers between code and challenging theory about how we should divide things up, remember "separation of concerns not separation of technology" so this is par for the course for them. Of course if you feel you do need that abstraction and explicit separation you are still welcome to write APIs and separate client side UI. But if that UI is the only consumer of that API then this may be a decent way to create it that's clearer, less complex and more performant. What's more if you further down the line realise you need the API then the pathway to going from server side to API led is probably a lot smoother than it was.
@tobiascornille
Жыл бұрын
How often do you do that though? I'd say for most indie projects that's not a big concern
@ricardocnn
Жыл бұрын
It's Laravel without reload
@ecel_style
Жыл бұрын
but you will never, it will never happen :)
Do you know what is good about api endpoints? Creating mobile apps that uses the same backend.
This is really awesome 😲😍🤩😌😘
I was just wondering about the three CSS http calls, are they necessary?
@amatzen
Жыл бұрын
Was wondering just the same, especially if they are identical, which I suppose they are.
@gaborkrisko
Жыл бұрын
@@amatzen in that case the are probably served from the browser cache
@senxo.visuals
Жыл бұрын
@@gaborkrisko They are not served from cache, because there's a different ?v=123123 on each of them, each time they load. But maybe it's due to the development/local server and how it ensures that files are always fresh?
@zuma206
Жыл бұрын
Just the Dev server, wouldn't happen in prod
She is amazing ❤
thanks 🔥🚢
you can use this with the src directory right?
Great video as always! but Isnt Remix doing this or somthing simular with loaders and actions?
@danielcooke3243
Жыл бұрын
yeah, next13 is entirely "inspired" by remix - and likewise the new routing system in remix v2 is inspired by nextjs13 - its a win win for all frameworks.
nice, i didn't know what all the hype was about, cheers for clarifying with the video
All of this is for s simple form handling :) hahaha nice one keep it up
if i am not wrong actions work only if your api routes are within the project? or they can be used if you have api routes somewhere else too?
Will the React course ever become a single purchase?
Yep, revalidate all page resources after every form submission. This is a revolution! P.S Already a year in remix and svelte 🤪
@nikmat
Жыл бұрын
React router dom v6 has it too?
@izzy7541
Жыл бұрын
@@ianbdb7686 it's not new and in react. Got a long time in remix
@henriquealmeida348
Жыл бұрын
Refetching everything is usually and actually a very good thing as you won't need to engineer complex situations. But, as far I understood in this situation, it will only refetch the specific component.
after seeing Remix, literally every framework after it implemented server action. and its good, the frameworks are better because of this feature. for anyone wondering about leaked credentials, just remember, if you are using it in a server component, then a leak is impossible since the code will never run on the client and the env will be undefined in the browser anyway if it is not prefixed with NEXT_PUBLIC_. If you are using server actions in a client component, then it may be a potential leak. But remember that server actions only run on the server + the envs will not be available if not prefixed with NEXT_PUBLIC_. And server actions are currently in alpha so their security will be improved in the future.
So this is better than it was? Still looks like a lot of code and things to keep in mind for such simple thing to do. It would be 5 lines of code in Sveltekit
Thanks dad!
Nice
The opimistic update feature is cool but it requires JS again, whereas normal form actions can execute without JS
You can do that without reloading via Laravel + livewire, Phoenix + Liveview, Rails + Stimulus, Django + Reactor and so on. As always they're reinventing features that existed for a while elsewhere and making it like it's a new thing. We're a ton to use React/Next because of its simplicity and because we actually want separation of concerns.
@YuriG03042
Жыл бұрын
it's a new thing in React, which is what Next is meant for. you are acting like they claimed to build a new base on the moon or something
@oscarcisneros1368
Жыл бұрын
Stop trying to sell us your shitty boomer frameworks
@heroe1486
Жыл бұрын
@@YuriG03042 It's in response to the Abramov's "With PHP you have to reload" And welll yes that's what they're trying to convey, just look at their Apple like conferences and overall marketing for things that have been here in other frameworks/PAAS for years, same for the "it's going to reshape the industry" kind of reactions from the public.
@buldezir
Жыл бұрын
Also same stuff exists in SvelteKit for quite a while
@heroe1486
Жыл бұрын
@@buldezir And apparently in Remix too
Will it replace react-hook-forms?
Ready to modify all backend code until the next update
everything looks great, but one thing has me thinking, how are we thinking about authentication? Like checking auth status in server actions, using cookies or tokens, login and register. I know you can say just use next-auth but that would increase too much dependence on a third party library.
@riddixdan5572
Жыл бұрын
that's what we call vendor locking
@oscarljimenez5717
Жыл бұрын
Middleware
@claritise
Жыл бұрын
You can use pretty much any authentication package you want? All you are doing is either decoding a JWT or doing a session cookie lookup.
Fullstack for the win
I'll be honest, when I first heard about all this I couldn't help but think how overcomplicated React was getting, but this video reversed my thinking.
Serious question, how are you so productive? How big is your team? Very impressed by your publication rate/quality
Okay, Remix has to step up their game
Server, server... The client side first was also useful
@axelramirezludewig306
Жыл бұрын
it's not 2017 anymore
@socketbyte5348
Жыл бұрын
@@axelramirezludewig306 yeah it's 2001
Difference between this and solid-start createServerAction?
i fucking love you Jeff Delaney
Seem promising but for now its painful to await a server action with revalidatePath then `router.back()` (to the list screen) to close a parallel routes modal.
Is there a way to set the default playback speed to .5 for this channel only?
@Ramon314
Жыл бұрын
yes, but why?!
I am starting with Next... why using frontend server actions to update database instead a dedicated backend? What is the benefit?
Oh look! Something SvelteKit already has! Nah it's actually a cool feature and I'm happy it comes to more frameworks! :)
@erickmoya1401
Жыл бұрын
Look what they have to do to mimic a small portion of our power
Those feature are the equivalent of Actions Form from Sveltekit right ?
Another great video that makes me to want to quit web development 🙂👍
@emilz0r
Жыл бұрын
😂
Someone correct me if I'm wrong, but I think the benefit of mutating directly on the component isn't that great considering that in any organized app we would have to write the logic in separate files, like we already do with Next's APIs. As for optimistic updates, the useSWR hook, which is also maintained by Vercel, is a very simple and effective tool to handle the rendering of API requests
@philheathslegalteam
Жыл бұрын
Ill say this. As a maintainer of an OSS library using SWR, server actions completely decimated its use case in web. For RN, and non next apps SWR is still useful, but in next 13 it’s completely useless. I almost discourage using SWR in next 13 app dir.
@Amaraticando
Жыл бұрын
server actions can be defined inside components, imported from other files or passed as props. This is not the same DX as using SWR or react-query.
Isn't that the same thing sveltekit does for svelte?
I keep getting Type error: Type '(formData: FormData) => Promise' is not assignable to type 'string' on my build. The issue is from this part action={updateProfile}>. Any idea how to fix?
when i import useOptimistic in next js application it says no module found. I am using stable next 14 version. do i need to do change or add some experimental flag for the same?
is it only possible via form? why cannot I call a server action from a button click?
Vercel's keynotes creep me out. It's like they're trying to be the Hooli of Javascript frameworks.
But how do you apply authentication on something like this? You need the header from the request, right?
if I have a sidebar layout that gets a data and I want to mutate in that data from another place, how can I do that?
Is “API first” principle obsolete nowadays? How can Server Components allow other clients to use the same backend? That was the whole point of SPAs, mobile clients communicating only over REST/GraphQL so that you can add more clients/automation/consumers later
@ghostlexly
5 ай бұрын
I think same as you, but looks like people don’t care and are just hyped
I would feel so filthy if I spent a day authoring code that winds up looking like this stuff
The use server it’s not the default value for components?
@skillm3h4ppy1er
11 ай бұрын
it is but you have to redeclare it when the function is in client component file otherwise the function will be a client one
hi kind of confuse how to implement an alert message after a successful submit update or insert using this "use server" components does anyone know how? ahahah
@jaiminparmar7996
Жыл бұрын
you need to do that in a client component
Yup, that's like Livewire in Laravel
🎉🎉
how can I upload files to s3 using server actions
haiyya don't use vercel kv, use normal sql mysql or postgres and prisma don't want vendor lock tho
@majorhumbert676
Жыл бұрын
Should be trivial to replace the function calls once you want to move to a different database
Is that the same feature Remix had since their beginning? Why cannot the frameworks just “borrow” thing from each other, but try are trying to reinvent the wheel “this time better”😢
Server actions cannot be used to communicate with a third party application. Say you have a Wordpress site or a React Native app that needs to leverage the NextJS backend, you would need API routes.
Man im behind. Been working on outdated tech for a while with no chance to try these new things
in 5:13 when he says button clicks the like and dislike button gets a rainbow border is this a new feature
PHP is waving
i knew that updog joke was happening 😂
Something about mixing server side code and client side code, in the same language in the same file, is giving me a lot of anxiety. I expect server secrets to be leaking a lot if this becomes popular.
@aakarshan4644
Жыл бұрын
they already did lol, i saw a tweet of people accessing server side env variable in client console
@agungokill
Жыл бұрын
php already did long time ago lmao
@MrMudbill
Жыл бұрын
@@agungokill php didn't use the same language for server and client, so it had better separation, if only marginally. But here since it's all JavaScript, simply forgetting to write "use server" feels like enough to leak something.
@agungokill
Жыл бұрын
@@MrMudbill that's the point, if php do it better why need something like similar to php again to some extent. just improve php to able to passing component tho
@MrMudbill
Жыл бұрын
@@agungokill I don't think I understand what you're suggesting
Why is the css reloaded loaded with rhe actions?
I'm not sure I like the idea of mixing server and frontend code together. Writing server-related code in API routes and serverless functions is more convenient, IMO. I really hope they won't deprecate "pages-components-api" way of writing applications in the future
@jezmck
11 ай бұрын
It seems extremely unlikely that they'd ever actively prevent you from doing it that way.
Isn't it labeled as experimental in the docs? I was going to try it, but then withdrew because of this.
Can someone explain why he used useTransition at 5:46, if that were a normal function, what would be the difference?
@icarojose6316
7 ай бұрын
It wouldn’t work. Because the functions like and dislike are actually server functions
Refetching assets?