I used all four in real projects. One wrecked a monorepo at 3am. Another saved my ass in production. Here's the unfiltered truth about every major package manager in 2025.
React 19's use() hook promises to replace useEffect for data fetching. That promise is partially true. There are two patterns with Suspense and error boundaries where the behavior isn't what you expect and the cycle gets messier. I'll tell you exactly when to migrate and when not to.
useEffect isn't broken — the mental model we teach with it is. I audited every useEffect in a React 19 codebase and found 4 concrete categories where it was an antipattern. Here are the patterns that replaced them: derived state, event handlers, use(), and Server Actions.
I ran all three package managers on the same Next.js 16 + strict TypeScript monorepo with Shadcn/ui and Radix UI. pnpm wins on disk and CI — but there's a real compatibility cost the migration guides never tell you about.
navigator.clipboard.writeText looks trivial until your app silently breaks in production with zero visible error. I found 4 cases the docs never mention: insecure context, lost focus, revoked permissions on iOS, and React timing. Here are the real patterns with copyable code.
Copy Fail hit #1 on Hacker News with 977 points. I reproduced it in my Next.js stack and found something the viral post never mentions: when the clipboard fails silently during a password or token copy, the user has no idea. That's not a UX bug. It's a human error vector with real consequences.
I scored 98/100 on Lighthouse and axe on juanchi.dev. Then I asked someone who actually uses a screen reader to try it. What happened next embarrassed me. A perfect score and a real experience are two completely different things.
32 years in the dev trenches. Here I write what I learned, what I broke, and what nobody tells you in the tutorials.
No spam. Unsubscribe anytime.