🤯 NextJS Server Actions - never write Post Requests again 

Thanks man! That's the kind of comments I'm making videos for :)

Yes, you can!

Do you have a sample link / codebox?

@@activenode Never mind, I made it work with useTransition. Man, you saved my life, I was trying make it work for 3 days and your video helped me a lot, please make more videos, you are great. Love you!

@@LtTheXamax Awesome! thanks so much 🙌

Yup because basically only a reference to that action is passed, not the action itself so to say.

Hey. Im working on more Videos 🙌

Can you specify what you're trying to do? Cheers

​@@activenodei have a api url in which i have to send some request body object through headers and then it give a data in the output in server actions this doesnt work but in axios method it works

It depends. Talking to your Python script can be done via NextJS Backend as both are Backend. If you have a Python only Backend being a Server in its own then you can also skip the NextJS Backend but also that removes the possibility of Server Action Usage

Sorry for the long wait, the comment didn't show in my dashboard. As you can see in the video, there is an onSubmit in combination with the action. In the onSubmit you can trigger the setState.

I think for this you might be interested in the other video which shows how we can trigger server actions. Hope that answers your question? If not, just come back again :) ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-6TRwsu0mUps.html

@@activenode im trying this but its not working import { authOptions } from "@/app/api/auth/[...nextauth]/route"; import { getServerSession } from "next-auth"; import React from "react"; interface Session { user?:{ data?: { access_token: string; }; } } export default async function fetchCount() { const session: Session = (await getServerSession(authOptions))!; const token = session?.user?.data?.access_token; console.log(token, 'ttt'); const res = await fetch('api-for-example.com ', { next: { revalidate: 0, }, method: "POST", body:JSON.stringify({ "stats": "current_user", "query_data": "yahoo.net", ..... }), headers: { "Cookie": `access_token=${token}`, "Content-type": "application/json", }, }); return await res.json(); };

Noted, checking what can be done.

Indeed! In general it's exciting to see that the tech world iterates including iterating back and forth. The only difference is the convenience it gets through optimal combination.

Are you using mutations with Cache Revalidation in your Server Action? In my case, without, it didnt reload styles.

@@activenode yes I'm using mutations, how can I mutate data without reloading styles? The data is fetched via api.

@@LtTheXamax Server Actions are still in Alpha so there might be new stuff incoming that solves the problem of a "general style reload". There is potential workarounds. I might make an additional video for that.

@@activenode that would be great, can't wait!

@@LtTheXamax Hope this one helps ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-6TRwsu0mUps.html

Coming soon in my next video

@@activenode looking forward to it!

@@andreaswu7973 Hope this one helps: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-6TRwsu0mUps.html In this video I am showing how to run actions manually and hence prevent the submission from client -> server. However: If your question was more related to: How to submit when no js is involved. (server-only) please tell me. I was thinking about getting deeper into server-only / progressive enhancements as well.

@@activenode hey thanks for this. if you plan to make a series about server actions that'd be great!

Hey, sorry for the late response, just seen it. The most common use-case is progressive enhancement (even though there's more). E.g.: You create a form with action=YourServerAction and it will both available on frontend (w/ JavaScript) and as well as a URL (without JavaScript on the Frontend). Even though, there's very few people disabling JavaScript, the reasoning behind it is that in our internet-everywhere world sometimes e.g. on the train, you can loose connection and the Frontend isn't loaded properly. Then backend will take over

Is that a good or a neutral feeling?

Yes!