#react

BestCodes I'm curious, what's the abstraction for? Like, why would I use this rather than the AI SDK's built-in tool approval?

NikitaKharya Great question! The AI SDK's built-in tool approval handles the core approve/reject flow really well. agenttrace-ui builds on top of that with two additional layers: Transparency alongside approval: The AI SDK provides a clear yes/no approval step. agenttrace-ui adds a more detailed view around that, with a collapsible timeline showing each step the agent took, the reasoning behind it, and the underlying data across multiple visualization modes. The approval step becomes one part of a broader, inspectable workflow. LLM-driven vs. predefined approval rules: With the AI SDK, needsApproval is typ

Amy Egan This looks awesome! 🤩

Aniket Pawar Thanks a lot Amy! ❤️

BestCodes I love this! It's cool how many theme options there are too 🤩

Pauline P. Narvas Cool idea! Worth sharing in this thread: community.vercel.com/t/whos-hiring-april-2026/37457

BestCodes @maximbuz This is interesting... I'm curious, where does the data come from?

Belty6979 5979 Really impressive how much you’ve packed into the calculator layer, especially keeping the calculations client-side while still maintaining a consistent UI across so many tools. I’ve been working on a simpler age-calculation tool as well, and one thing I’ve found interesting is how much the experience improves when the result shows the exact breakdown rather than just a single number. Projects like this make it clear that calculators can be useful standalone tools, not just small features inside a larger app. For anyone interested in seeing a more focused example of that approach: myagecalcula

BestCodes Really interesting! I see it mentions Expo for mobile support on the website. Does it support iOS?

BestCodes Must say, my portfolio looks pretty sick 😏 However, I do notice that some of the images are broken or not loading. Any idea why that's happening? Great job @skb3611 😃

Skb3611 You need to provide the images for your projects (the best ones that you use for marketing) or else im thinking of adding the github repo banner as default , what do you think?

Jonoroboto TL;DR: it’s faster, dev server go brrr, go upgrade

ADALIGO This looks like a solid iteration on Next.js Jonoroboto. The Fast Refresh change (module-level re-execution) is probably the most impactful here, aslo reducing unnecessary invalidation across the import graph has a real effect on dev feedback loops. Curious how consistent these gains are at scale and how this holds up on larger apps though?? especially with Turbopack already in place. But overall, seems like one of those low-risk, high-impact upgrades 🚀

BestCodes @jonoroboto I enjoyed reading that (hopefully I'm not a dummy 🫠)! Also your website is amazing! 😃

BestCodes Oh no, is the website down? 🥲

Pauline P. Narvas Looks great! Thank you for sharing 😃

@amd Looks good

Hugo Lin Thanks for your loving!

BestCodes This is a fascinating idea, but I wonder if it's a necessary abstraction 🤔 Definitely interesting! Keep up the cool work 🔥

Pauline P. Narvas Cool project! Thanks for sharing with the community :)

Pauline P. Narvas Hey, @lennsend170683-4600! Welcome 👋 Quick debugging steps: Open browser DevTools Console and check for errors when switching tabs Look for event listeners on window.blur, document.visibilitychange, or similar Try disabling browser extensions that might interfere Check if the issue happens in all browsers or just one For a proper fix, you’ll likely need to update how your CRM handles state persistence. Let us know!

Lennsend170683 4600 Hi Pauline, I honestly have no idea what Im looking at sorry. Is this any help? Regards Lenn

Lennsend170683 4600 @pawlean not sure if that was any help at all?

Tianen Pang check this one github.com/vercel/next.js/issues/89764#issuecomment-3928272828 for temp fix

ADALIGO The error comes from tooling mismatch not from you Luknuts56, just downgrade ESLint and you’re good 👍

Ryu Hi Luknuts56, This one looks like a tooling-version mismatch, not a problem with your loading.tsx file. Your package.json has: and the stack trace is failing inside eslint-plugin-react while loading the react/display-name rule. There’s an open Next.js issue for this same ESLint 10 error: github.com/vercel/next.js/issues/89764 For now I’d pin ESLint back to v9 instead of using ESLint 10: If it still keeps ESLint 10 because of the lockfile, do a clean install: One more thing: since you’re following a course, I’d avoid using "latest" for next, react, and react-dom. The tutorial may have been writ