vercel-react-best-practices

To optimize React and Next.js performance, apply targeted best-practice rules across data fetching, server actions, and component rendering to reduce waterfalls and accelerate SSR/CSR. This approach generates safe, testable refactoring changes without altering functionality.

Refactoring React Server Components (RSC) and client components for bundle optimization involves applying category-specific rules to minimize server/client overhead. This reduces bundle size and improves code robustness by detecting anti-patterns and enforcing safe code generation patterns.

Yes, this React performance refactoring approach works with existing Next.js pages and data fetching patterns by identifying anti-patterns and applying optimization rules. It safely generates testable changes across codebases without altering existing functionality.

Detecting anti-patterns in Next.js server actions and data fetching logic requires applying a comprehensive set of 57 rules across 8 categories. This automated analysis identifies performance bottlenecks and generates actionable refactoring tasks to improve code efficiency.

The limitation of using static best-practice rules for React performance improvements is that they focus on pattern detection and safe refactoring without altering functionality. Complex, dynamic runtime bottlenecks may require additional profiling beyond these 57 categorized rules.