The problem with server actions
Vložit
- čas přidán 6. 06. 2024
- Astro Actions add the BEEF to server actions. Try them out: astro.build/blog/astro-490/
Use Upstash for Redis NOW: upstash.com/
#javascript #react #next
Music from #Uppbeat (free for Creators!):
uppbeat.io/t/dan-barton/the-e...
License code: LRSQGNFHDV0YWIDM - Hry
This man is the greatest product person in history... the charisma, the charm, the technical expertise!
Darn, the men not only makes good content, dunk memes on the community but manages to make insane actual production code in the process. Adopt me please
Sorry this component does not accept children
Ah you forgot to add the children prop in the types 😂
@@bholmesdevspat my coffee laughing 😂
Astro comes to solve all the details that we like .
this is one aspect that i like when framework compete with each other, initially react introduce us to server action, then nextjs as an early adopter showed us how it could be implemented and what benefits it brings. then other framework (in this case astro) perfected the ideas and the implementation even more from what it learnt from nextjs. im curious as to what new things/ways the remix team will bring to the ecosystem.
these framework will learn from other framework what works and what doesn't works and keep building upon those ideas, eventually innovating better and better ways to do things
Awesome video - earned a sub. Very rarely do you see content this fun in the advanced tech world
Man I live these kind of formats! good luck with that 😆
This channel should really have much more subscribers
Whenever you present something everybody learn it immediately haha, really nice video 🙌🏻
I always wanted to make a presentation exactly in this style at my job, I'm glad someone had the same idea
Ben is on 🔥 lately
Wild... I gonna be trying this with a few endpoints I'm currently rolling for course enrolments and stripe
Absolute legend!
Haha fun way to do this. I like the dev event style.
Well well well what's up with the intro? hahahaha well done!
This is actually fire !!!!
this is amazing
i think i fell in love with the astro corp
It looks wonderful except for the disgusting requirement of ZOD and that "safe" should be the default. People must understand that exceptions need to be... The exception
I’m open to safe being the default! Seems most people reach for it in practice
@@bholmesdev probably a getUnsafe is more clear and makes people think more about what it entails
Really nice!
This is insane
What a great fucking intro dude. Unbelievable 😍
Actions with a TRPC-like API! 😯🤯
How do you not have over a million subscribers??
why im not subbed to you, lemme just fix that
Holy fuck man now this is content
Great vid man, I would LOVE to know what vscode theme your using!!!
Thanks! It's Astro's own Houston theme marketplace.visualstudio.com/items?itemName=astro-build.houston
so what is your choice when it comes to javascript frameworks Ben?
how about determinate progress by uploading file can we use it in server action?
Finally a framework which adds complete features and thinks about real developer scenarios. Not some half-backed ass shit figure out and get fucked features (I'm looking at you, nextjs)
What is your VS code theme? :p
I wish safe was the default and unsafe existed as escape hatch
I've heard that a few times! Also find myself using .safe more time than not. I think flipping to the default and adding an orThrow() for the alternative is a good change
Astro Will supports other schema libraries like valibot or effect/Schema?
vv good video!
vv much appreciate that!
Meanwhile php still paying the bills of deva since ages
I am moderately new as a dev... a few years. I have never found a use case to make php worth it... yeah, it's in a lot of legacy code... but I can't see why someone would reach for it first anymore.
@@patrickjreid Take a look at Laravel + Inertia + {insert your JS framework}. All this back-end + front-end glue code problem (and front-end routing) is basically solved.. It's pretty awesome. PHP + Laravel has a great ecosystem and the community is pretty alive, PHP is not only legacy systems and Wordpress anymore
Love the Vsauce references
💚🔥💚🔥💚🔥💚🔥💚🔥
This might not be the most relevant place to place this concern but I have been working with astro and really enjoying it... BUT when using it with a headless CMS (which most astro sites will have) It is not very straight forward to set up a live preview or visual editing, because of the nature of SSG it seems like this is either only possible using CSR or SSR and then having to separate deploys for previews (SSR) and one for the prod site (SSG). So my maybe this is better to ask of the CMS companies to make a process to set up live editing without this level of friction? Anyways if anyone knows a way around this, or have dealt with this before let me know. I am using Sanity currently but an example with any headless CMS would be fine. Seems like once again SSR is pretty much required to do useful things.
This has definitely come up! Vercel is the only host I've seen "solve" this with a dedicated draft mode. Otherwise, I agree we could have some sort of SSR-only-in-preview setup docs.astro.build/en/guides/integrations-guide/vercel/#excluding-paths-from-caching
How old Are you ? Good explanation 👏👏
I love the spectacular millennial nerd memes
No Chick-fil-A sauce?!
minecraft mentioned lfgo
let num = isNaN(+str) ? 0 : +str;
gooch()
😂
Cornier than @t3dotgg's hair (the intro that is) 😂
Cloudflare is far from being the cool kid on the block..
I'd beg to differ czcams.com/video/_dtyYDwHAIc/video.html
How you settings in top of the vs code 🥹🥹🥹
In the documentation in the Routes part of Astro, it is very conventional the way it is done in NEXT, I simply hate the applied convection, it completely takes away the freedom of customizing the url, I use Vitejs and React with react-router-dom, I was able to configure it smoothly routes like any-coisas.localhost:3000/ or any-coisas.localhost:3000/slug,,, this in astro is quite annoying to configure and I don't even know how the urlr prefix would be done, something like maria.localhost: 3000/home I like having the freedom to define my routes and not pass data through parameters in the url but control via state... This was the annoying part of Astro that I've seen so far
I find Astro Design terrible, I will stick with Next.js which is industry standard SSR