Ravi

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)

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

once again, opus 4.5 failed to fix a bug, ultrathink didn't help, kicking off multiple sub agents to research the issue didn't help, new context windows didn't help, trying in gpt 5.1 codex didn't solve it. what did fix it? one prompt to gpt 5.2 😀

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

@RaviCoding @aisdk @tan_stack What you see in TAI is alpha. As you may know, we care *a lot* about rerenders and perf, so expect our underlying mechanics to evolve pretty quickly on this front.

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?

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.

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

almost time to hack

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

@codewithantonio I actually started a tool for this (@vibestackcli) , but started having some doubts and stopped working on it for now... x.com/RaviCoding/sta…

I NEED THIS npx shadcn add <auth> - working auth with components, pages, API npx shadcn add <billing> - working billing with components, pages, API npx shadcn add <feature> - working feature

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

After 5 years, I just finished my last week at Vercel 🥲 What a ride. I'm grateful for this community and proud to have helped people learn to code with React/Next. Many tweets sent and friends made. I guess I don't have to wear all black now!? Gotta switch up my wardrobe...

@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.

I love building APIs with @honojs ◇ Blazing fast ◇ OpenAPI specs ◇ Validated body, params, and response ◇ Scope middleware Generated SDKs with @speakeasydev

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

@RaviCoding @trpcio @nextjs Quick question - how do you handle global errors? Like Toaster on Queries.

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

@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: github.com/perfectbase/ne…

@RaviCoding @nextjs Please, I was just looking for this, my next.js app is slow as heck, I tried everything database Pooling caching everything. Planning to switch to tanstack if nothing works.

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.

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.

@RaviCoding @nextjs How does video 1 happen? I’ve only experienced the behaviour in video 2, where visiting an already-visited route shows immediately

@codinginflow My tweet from a few months ago for context: x.com/ravicoding/sta…

@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!

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

Thanks for making this @iamsahaj_xyz

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

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)