The release of React 19 brings exciting new features and patterns, but it also creates immediate friction for development teams working with existing ESLint configurations. Many developers encounter warnings about deprecated or unstable APIs that were once acceptable, particularly around default props patterns that have been standard practice in React codebases for years. These warnings force teams to make difficult decisions: update existing code, ignore the warnings, or find a middle ground that balances modern best practices with practical development needs.
React's stability classification system has evolved, and what was once considered a stable feature may suddenly carry an 'unstable' label alongside expiration policies that create uncertainty. The ESLint framework struggles to keep pace with these rapid changes, often lagging behind React's release cycle or providing conflicting guidance about which rules are essential versus optional. Teams find themselves questioning whether they should adopt every warning as a hard requirement or treat some as suggestions until the ecosystem matures.
This challenge becomes particularly acute when managing large codebases where updating every component pattern would require significant refactoring effort. Understanding which React 19 ESLint rules represent genuine improvements versus transitional suggestions helps teams make informed decisions about their migration strategy. At Paradane, we've observed that the most successful React upgrades involve strategic rule adoption rather than wholesale configuration changes.
