Ankita Kulkarni

Yeah will def check it out

The Modern Full Stack Next.js Course An online course that teaches you modern full-stack NextJS 16 and how to build Production-Ready apps to take your web development skills to the next level.

This is part of the Modern Full Stack Next.js Course: ship 7+ production-ready apps.

Free lessons: dub.sh/how-does-ne...

A terminal command prompts the Next.js Bundle Analyzer, creating an interactive Treemap visualization for analyzing production bundles.

Is your Next.js app feeling sluggish or taking forever to load?

Try the experimental Bundle Analyzer, an X-ray for your app

Get an interactive Treemap of your JS bundles → Find the culprits

🎁 Free lessons: dub.sh/how-does-ne...

Stop wrapping your entire Next.js page in "use client"

Just because ONE component in the page needs interactivity

You'll turn the entire page into client components

Solution:
✔️ Extract only the interactive piece into its own client

🎁 Want more? Download the FREE Cheatsheet
dub.sh/nextjs-mist...

Your AI agent keeps making the same React mistakes over and over

You need to use Skills

Skills are the NPM for AI Agents

You install best practices like you would a npm package

→ One command and your agent follows 10+ years of patterns instead of guessing

🍿 Full breakdown: dub.sh/npm-for-ai-...

This ONE concept is killing your app's performance

Every component is a Server Component by default in Next.js

You're shipping Client side JS when you don't need to

🎁 Here's a FREE lesson covering,
✔️ Server Components basics
✔️ Their purpose
✔️ When to opt out

→ dub.sh/server-comp...

Terminal-style code showing "git worktree add ../app-hotfix -b hotfix/login" with a note about running multiple agents in parallel using Git worktrees and an author credit.

Running multiple AI agents on the same project?

The moment one switches branch, the other breaks

Thats because Git only allows one branch checkout at a time

The fix?
→ 𝗚𝗶𝘁 𝗪𝗼𝗿𝗸𝘁𝗿𝗲𝗲𝘀 ⚡

Each agent gets its own folder, its own branch, same repo

🍿 Full breakdown: dub.sh/git-worktree

🚀 @kulkarniankita.com is speaking at #ReactParis 2026

Discover the #toolkit and #architecture for creating #AI Minions; autonomous #agents that fetch data, trigger workflows, and scale like real teammates in #nextjs apps...

Learn more 👉🏼 React.Paris

#conference #speaker #reactjs

How I realized the workplace is toxic

youtu.be/_-Tj3bPSYCI...

2025: Year in Review | Semantic Fish Creative Group This post gets personal about my experiences this year with grief, loss, health emergencies, and being disabled & working in accessibility in the US.

I've had an execeptionally tough year.

I have no income or health insurance, and could really use your help finding my next paid project. 💜

semanticfish.com/2025-year-in...

Open to front-end, full-stack, design system, & accessibility projects. 10+ years experience.

Many more details in post!

Writing my last newsletter of the year!

Kevin Powell Helping you learn how to make the web, and make it look good while you're at it. With weekly videos and shorts, I'll be bringing you How Tos and Tutorials, as well as simple tips and tricks, with a b...

@kevinpowell.co is only 4K subs away from 1M subs, let’s support him.

If you don’t subscribe, please do as he is the best and I learned a lot of CSS tricks and tips over the years!

Subscribe here 👇

youtube.com/@kevinpowell

Kevin Powell Helping you learn how to make the web, and make it look good while you're at it. With weekly videos and shorts, I'll be bringing you How Tos and Tutorials, as well as simple tips and tricks, with a b...

@kevinpowell.co is only 4K subs away from 1M subs, let’s support him.

If you don’t subscribe, please do as he is the best and I learned a lot of CSS tricks and tips over the years!

Subscribe here 👇

youtube.com/@kevinpowell

a mistake I see constantly: leaders go quiet when something went wrong

in the absence of the real story, people will try to piece the story together from incomplete information

a story always gets told. rumors are usually worse than the truth. be vulnerable: own it so you have a chance to recover

plenty of fixes deployed to rscexplorer.dev, but mostly i just feel a lot better about the code itself

I don't think we'll struggle with having too many ideas that we can't implement anymore

Instead, we'll struggle with building too many things and can’t focus on one thing

Why can't I change port in Tanstack Start with Vite just by "vite dev --port 6000" and no port 6000 is not taken 😭

Wish I was in Portland!

Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week.

These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.

@clerk.com Billing is all I need for my SaaS

They offer pricing tables, waitlists, user management all in one.
Why do I need 10 different providers?

And before you comment, you don’t own your users. Stop as they offer a download option to get all your data

Really impressed 👏

So excited about the video I’m dropping next week!

Finally settled in my new apartment and man, it feels so good to get back in the routine!

Server Components is not really related to SSR. I like to think of Server Components as componentized BFF ("backend for frontend") layer. Each piece of UI has some associated "API" with it (whether REST endpoints, GraphQL, RPC, or what have you). Server Components let you express the dependency between the "backend piece" and the "frontend piece" as an import, instead of as a `fetch` (client calling server) or a <script> (server calling client). You can still have an API layer of course, but this gives you a syntactical way to express that there's a piece of backend that prepares data for this piece of frontend. This resolves tensions between evolving both sides: the each piece of backend always prepares the exact data the corresponding piece of frontend needs because they're literally bound by a function call (or rather JSX). This also lets you load data as granularly as you want without blocking (very nice when you have a low-latency data layer). Of course you can still have a traditional REST API if you want. But you can also have UI-specific server computation in the middle. There's inherent tension between the data needed to display the UI (a view model) and the way the data is stored (database model); RSC gives you a place to put UI-specific logic that should execute on the backend but keeps composability benefits of components.

maybe not the best moment for it but i finally condensed my “why react server components” into a short blurb that does well on HN

Critical Security Vulnerability in React Server Components – React The library for web and native user interfaces

There is critical vulnerability in React Server Components disclosed as CVE-2025-55182 that impacts React 19 and frameworks that use it.

A fix has been published in React versions 19.0.1, 19.1.2, and 19.2.1. We recommend upgrading immediately.

react.dev/blog/2025/12...

That’s great, Yeah It is incredibly useful!

pre Turbopack, we had "webpack_internals" in browser dev tools, does anyone know how I can see what files gets shipped to the browser now?

it was easier to see "mark something use client and it gets included in the bundle" but don't see that anymore

See you there!

The Full Conference Speaker Lineup ➕ Agenda are Live! 🔥

The ultimate #ReactParis 2026 squad is here; ready to blow your mind with cutting-edge #talks, deep dives, and game-changing insights.

ℹ️ All you need to know about this 2026 edition #programme 🧾 in the first comment 👇🏽

***Correction: server only is not a directive but a package

Ahh yes my bad, Yes you are right! Thanks for catching that

Next.js 16 Deep Dive Cheatsheet

Get a free Next.js 16 Cheatsheet here: dub.sh/nextjs-chea...