|
Hey Reader,
There are thousands of you going through Modern Full Stack Next.js Course so wanted to be grateful here for your support.
Just as a thank you, there is something big dropping for you. It will only last 24 hours ⏰ so keep an eye out for my email next week.
Let's dive in!
|
PRESENTED BY CLERK
Instead of your coding agent guessing how auth works, you can now install specialized Clerk knowledge directly into it.
Introducing Clerk Skills
One simple command
$ npx skills add clerk/skills
That’s it!
Now your agent can: ✔️ Add Clerk auth to your Next.js app ✔️ Build custom email/password flows ✔️ Set up organizations for your B2B SaaS ✔️ Sync Clerk users to your Prisma database ✔️ Even generate Playwright tests for auth
And it works with Claude Code, Cursor, Copilot, Codex, Gemini CLI… basically your whole AI stack.
If you’re building modern SaaS apps (especially B2B 👀), this is the kind of leverage that saves hours and prevents subtle auth mistakes.
It’s completely free to try! ⭐
|
🍿 Our Weekly Snack: You’re Suspending the Wrong Component
If you’ve been working with Server Components + Suspense in Next.js, this one is one of the most common mistake I've seen my students make in my Next.js course.
Now, lets you display a fallback until its children have finished loading.
The Problem
Let's say, you fetch data in an async component… then add inside it, around the JSX you return.
That won't work.
Why? Because Suspense catches suspensions from its children. By the time your inner renders, the await has already happened, there's nothing left to catch.
✔️ The Fix
Move the boundary one level up to the parent component. Wrap the async component itself, not its contents.
Here's how,
Now, → Parent renders with inside → Async child suspends during its await → Parent's Suspense catches it → Loader actually shows.
💡 Takeaway
If your loader isn’t showing, check the level of your boundary.
Suspense needs to wrap the component that suspends, move it one level higher, not lower (often fixes it).
|
🚀 Latest Frontend News
Your App can Reach 250+ Million Devices, Here's How
Next.js Finally has Competition, an article that breaks down how the competitor is better
This is a Powerful TypeScript library designed to help developers easily create complex, synchronous, and asynchronous programs.
We swapped one dopamine loop for another, Token anxiety is a super powerful post.
Spotify says it's best developers haven’t written a line of code since December, thanks to this one thing
Long-running agents are now available in Cursor
Introducing TanStack HotKeys, Setting up keyboard shortcuts is supposed to be easy and this library gets it.
There is now an official MCP for Excalidraw (one of my favourite white boarding tools)
TanStack AI has dropped a new adapter for Fal.ai
Is Figma too late to the AI game? They just dropped Claude Code to Figma MCP
With React Doctor 💊, you can scan your React codebase for Anti-patterns, run as a CLI or agent skill
The future of Next.js isn’t just better DX for humans, it’s better DX for agents, with structured logs, agents.md, and built-in context so your AI stops hallucinating and starts shipping.
A static checker for GitHub Actions workflow files
|
🙏 Your Feedback helps shape the newsletter
A few of you shared feedback last week that the newsletter felt very AI-heavy. That’s fair.
AI is changing how we build, ship so you’re going to see me talk about it. But I also hear you.
Web fundamentals, frameworks, performance, architecture, that’s not going anywhere. I’ll be more intentional about keeping a healthy mix so you get both.
Now, make sure to keep sharing your feedback by clicking one of the links below. I'm listening 👀 .
🔥 Love it!
😐 It’s okay
👎 Not good
|
If you’ve published a blog post or shipped something, feel free to reply to this email and it comes straight to my inbox. I’m always looking for great community work to consider featuring. |
All past newsletters can be found here. You can email me at me@kulkarniankita.com to advertise/sponsor the newsletter.
For those curious, I write all my emails using Convertkit.
See you next week!
|