que grande Jack, este contenido me sirve mucho!

How about React Query !?

This project is worth Trying. every bit of it

How would you add a pending state in this structure? Adding useFormStatus to the shadcn button doesnt work

Is this coming soon like Turbopack is, or like... actually soon?

Having issues with this 🤯 ```$ concurrently wsrun --parallel start [0] /bin/sh: wsrun: command not found [0] wsrun exited with code 127 error Command failed with exit code 1.```

That looks like a whole mess of gnarly boilerplate, compared to what I'm seeing in Preact signals. I'm excited about this evolution, especially because useEffect is so messy, and you're otherwise left with a myriad of non-standard, third-party options that may not be around for years. Signals brings simplicity and maturity to React, which is desperately needs. I'll wait for the standard to make it into JS and trickle down through all the frameworks.

In real application should we share the whole app component of each remote app, and download it lazy? And how can I implement nested routing in this case?

Hi Jack! Is there any way or make sense to do something like export type DiscriminatedAction = { [K in keyof typeof someActions]: { type: K; payload: SomeState[K extends keyof SomeState ? K : any]; // trying to define this in order to get the actions from an object and my State shape interface }; }; export const someActions = { SET_DATA: "SET_DATA", SET_SOMETHING: "SET_SOMETHING" } as const; dunno if is better just type the discriminated union with the types of: (E.G) typeof SET_DATA

hey Jack! Great video! I followed your fix for the "React form was unexpectedly submitted" case, but now as I tried to add the useFormStatus hook, it doesn't get aware of the pending state, because we are basically making our way around the "action" prop itself. Do you have an idea to solve this? Thanks!

Shadcn

I was looking for this kind of video for so long. worth watching every second.

Great video , i learnt a lot of new tricks thank you , but i have one remark , you can give the server actions data returned from validation directly without transform it to formData 😅

Hi Jack, I'm reading your book and wanted to implement pattern with suspense+error boundary, however in my next.js project catching error caused by offline microfrontend consumed by the container doesn't work. I also tried using dynamic from next but didn't work either. Is there some way to display fallback when mfe is offline in next.js app?

Wait are we back to just the root called bootstrap?? 😊

cool

Best video for a basic understanding of micro frontends.

cool

Teacher Jack, question. Does subscriptions still work at scale? What if there are two server pods?

Sign in... Telemetry.... Ok. No thanks, I use the terminal for serious things.

TDD sounds great in theory. Even better than communism.

plz create more such advanced topics

Course update??

Electron webdev garbage proprietary shitware.

who uses github for logging in?

what about vectorise a screenshot and use visual copilot ?\

Why TF everyone include tabnine ? Tabnine is anything except AI. It has an early mover advantage but its suggestions are doog poop. It was a bad tool when no other tools were there and now it's worse.

what is that VSC extension,so cool ? Can anyone tell me ?

Yeah, really like of Zustand.

window - is the best state manager

Thank you very much my dear professor. Necessary this update, a few days ago I had tested the next-auth: "5.0.0-beta.16" and there was some problem with the middleware.

Good video, but for somereason I've been getting error of "A React form was unexpectedly submitted." with this approach.

Great content, as always.

great content, but unfortunately the solution is not working for me "Uncaught Error: A React form was unexpectedly submitted. If you called form.submit() manually, consider using form.requestSubmit() instead...." but unfortunately requestSubmit is not working at all

can you create an extend tutorial about refresh token?

Thanks, is Next-Auth v5 support mobile login(react native)?

Kind of exciting! I wrestled with v5 for a bit a few months ago, and it had a ways to go. I was trying to work with the token and providers and had to do some hacky stuff to get it working.

This is too advanced for me. Pace is way too fast and got lost in the sauce way too quickly. Based on the comments it seems its well explained but ... yeah 😪 I feel l understand better when I see things built in real time rather than this highlight method... gives my mind some space to process things up as they appear on screen rather than being shocked by a snippet of code on screen and have it being explained real time without me having any type of context prior even if I stop the video to read the code first... anyway... I guess I'm not at this level yet womp womp

Question: How is the form resetting? I even downloaded the github code and ran on local machine. It does not reset form after successful submission. And how do i use function like form.reset()? Also 'status' only shows previous state if rendered outside of form. There are some many issues with this approach, I think it is not yet ready for production.

an even better example is to use <a>'s href

Don't leak email

Hey Jack, great video as always, I wished you added an implementation on how to update the session both client & server side at once, I would love to see how you handle this one.

AFAIK the default base path is already api/auth

It is not working on app router. Do you have any fix for it?

Thank you! ?: We don't seem to use <SessionProvider \> if we can and do get session on every component. Do we really need it?

we herr

I've been working on a project for school and I've recently been trying to find a simple auth solution. It just so happens that this video comes out today! 14 hours ago!! I'm amazed and pleased to say the least. This is perfect. Thank you so much.

I've used Nextauth a lot but curious about Lucia as well. Thanks for another great video!

Where is the formdata type coming from?

Been really struggling to understand the purpose and use-case of API/ROUTE with Next. This video single handedly has gotten me to rethink my entire DB architecture. MASSIVE thank you