-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Bump The Project To React 19 #45
Comments
Will this create a dependency? wondering if may create issues if installed in projects that haven't migrated to React19 and may not (many) |
@Vanals Upgrading to 19 will most likely introduce problems like that, but since not all the dependencies already used in the components have good React 19 support, it will be a while before I'll tackle this, so for the time being any component you copy to your projects will continue being a React 18 component. Maybe we could add a version picker to the website to support react 18, but that is a big stretch. |
@DavidHDev I have just added the ability to have 'peerDependencies' in the registry. This allows you to give warns like: This might be useful while you are still working on React 19 support. And whenever you move off of 18 and want to support >= 19 |
@ieedan thanks for letting me know, do I need to do anything to enable this? |
Yeah just add the key in the config file and rebuild the manifest. (It can accept the same style of versions as npm) https://jsrepo.dev/docs/setup/registry#Peer%20Dependencies What this looks like for one of my projects: |
Description
The current React version used by this project is
"react": "^18.3.1"
.Proposal
Upgrade the project to React 19 to take advantage of the latest features, performance improvements, and bug fixes. Ensure compatibility across all dependencies and address any breaking changes.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: