chore: upgrade to React 17 with v7.0.0 release #415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 React 17 Migration (v7.0.0)
This PR modernizes the library to support React 17 as the minimum version, along with updating the entire toolchain to current standards.
What Changed
React & Dependencies
peerDependenciesto React 17.0.0+devDependenciesto React 17.0.2"jsx": "react-jsx") — no moreimport Reactneeded in every fileTesting & Tooling
@testing-library/reactto v12.1.5 (last version supporting React 17).husky/directory setup)lint-stagedto v15 for Node 18 compatibilityCI/CD & Node.js
engines.node: ">=18.18.0"to enforce minimum versionWhy This Matters
React 16 reached end-of-life, and the ecosystem has moved on. By setting React 17 as our baseline:
Breaking Changes
Migration Guide
If you're on React 16, you'll need to upgrade to React 17 or later before using v7 of this library: