Ravi

Trying to create high quality tutorials on YouTube.
Building @edgestorejs.

[Ravi @RaviCoding]

Improved @edgestorejs dropzone components just dropped!!!

✨ Beautiful
🚀 Feature rich
🔧 Completely customizable
💻 Install with the @shadcn cli
🛠️ Open in @v0 integration
🗄️ Provider agnostic (no need to use with EdgeStore)

[Ravi @RaviCoding]

@webdevcody I also switch to gpt 5.2 for hard bugs…
Opus 4.5 is still the best default model though, IMO.

[Ravi @RaviCoding]

@tannerlinsley @aisdk @tan_stack I know that if someone can make it better it you guys!! I can’t wait for the stable version!

[Ravi @RaviCoding]

Quick share of my current thoughts on the @aisdk and @tan_stack AI.

I've been using the ai-sdk for a while and I really like it overall.
That said, my biggest pain point is how useChat works.

Since all state lives inside a single hook, every component that uses useChat re-renders on every new streamed token.
The current workaround is putting useChat in a lightweight wrapper + prop drilling + component memoization to avoid re-renders. (not a great DX).

There are community solutions like ai-sdk-tools/store by @pontusab, which syncs the context into a Zustand store so you can selectively subscribe. Which is cool, but it feels like something we shouldn't have to build ourselves.

When I heard about TanStack AI, I expected a TanStack Store style approach (similar to TanStack Form) with fine-grained subscriptions.
But from the docs, it looks like it uses the same useChat pattern.

Now I'm curious...
Am I missing something?
Is there a better way to use these libraries?
Or is this issue rare enough that it's not worth improving?

[Ravi @RaviCoding]

https://t.co/RAh3fkiek9

[Ravi @RaviCoding]

If you use @nextjs you'll want to watch this one!
10 different ways to make your Next.js app navigation FAST!
Let me know what you think.

[Ravi @RaviCoding]

@peduarte Welcome to Japan! Looking forward to meeting all of you!

[Ravi @RaviCoding]

@codewithantonio @vibestackcli It actually already works, and people can add their own custom markdowns to be added to the project.

[Ravi @RaviCoding]

@codewithantonio I actually started a tool for this (@vibestackcli) , but started having some doubts and stopped working on it for now...
https://t.co/EMOF6O4piu

[Ravi @RaviCoding]

https://t.co/tCXNnN49th

[Ravi @RaviCoding]

@leerob I can’t help feeling kind of sad about it… but I hope you all the best to whatever comes next!

[Ravi @RaviCoding]

@pontusab @honojs @speakeasydev I’ve tried both hono and orpc recently for rpc+rest integration. I ended up deciding to go with orpc. The DX felt a little better.

[Ravi @RaviCoding]

@FrankCodeZ @trpcio @nextjs For showing toaster on mutation errors, this is what I do:

[Ravi @RaviCoding]

I love my shared error handling for useMutation with @trpcio and @tan_stack query. 🤩

[Ravi @RaviCoding]

I'm really enjoying my <Await> component for prefetching @trpcio queries in @nextjs server components!

[Ravi @RaviCoding]

@JayanPaliwal @nextjs It���s still going to take some time to finish the video. But you can take a look at the repo if you want: https://t.co/u5tINN6dmK

[Ravi @RaviCoding]

I just made 10 examples of the same app to show different ways to improve navigation performance on @nextjs.

I'm preparing a video to talk about it. 📽️
Let me know if you're interested in watching it.

[Ravi @RaviCoding]

Video 1 is the simplest sample app. Using the latest next.js with the App Router and Suspense wrapping the dynamic components. If you're experiencing cached client routes, maybe you are using next 14, which caches visited dynamic pages for 30 seconds by default. Next 15 doesn't cache by default, so if you're experiencing this on 15, you probably have some caching configured somewhere.

[Ravi @RaviCoding]

@codinginflow My tweet from a few months ago for context:

https://t.co/AfJ8jiZsKd

[Ravi @RaviCoding]

IMO, the things that make @PlanetScale hard to beat are:
• Non-blocking safe migrations 🚀
• That awesome dashboard for analyzing & improving queries 📊
• Weekly performance reports are super handy 📈

Unfortunately, there are disadvantages…
• No free plan anymore 😭
• No PostgreSQL support 💔

[Ravi @RaviCoding]

Wow!! I really wanna try this one out! 🤩

[PlanetScale @PlanetScale]

PlanetScale now supports Postgres.

[Ravi @RaviCoding]

@codinginflow No DB service has been able to match PlanetScale’s user experience. If they can offer the same experience with Postgres, it will be really great!

[Ravi @RaviCoding]

Thanks for making this @iamsahaj_xyz

[Ravi @RaviCoding]

Just used tweakcn for the first time. Enjoyed it a lot! Very useful and has a very nice UX!

[Ravi @RaviCoding]

Upgraded all of the core packages and refactored the whole @edgestorejs dashboard codebase to improve navigation performance while also making it easier to maintain. I'm proud of this one! Hopefully I didn't break anything. 🤞
(@nextjs)