-
Notifications
You must be signed in to change notification settings - Fork 39
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
react 19 not supported #85
Comments
Why is this library, which has vast potential, not maintained? |
Duplicate #82 |
smnbbrv
added a commit
to smnbbrv/react-advanced-cropper
that referenced
this issue
Jan 30, 2025
close advanced-cropper#85 and advanced-cropper#82 . I already use it with react 19 and haven't seen any issues
Because I have a very heavy workload at the moment. But I hope I will find the way to improve the situation. |
@PanditSiddharth , @Ashkar2023, @k1rana it should be fixed in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PS C:\Users\mynms\Desktop\ignoux\ignoux> npm install --save react-advanced-cropper
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: ignoux@0.1.0
npm error Found: react@19.0.0
npm error node_modules/react
npm error react@"^19.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.0 || ^17.0.0 || ^18.0.0" from react-advanced-cropper@0.20.0
npm error node_modules/react-advanced-cropper
npm error react-advanced-cropper@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users\mynms\AppData\Local\npm-cache_logs\2025-01-06T09_07_41_100Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users\mynms\AppData\Local\npm-cache_logs\2025-01-06T09_07_41_100Z-debug-0.log
please update
The text was updated successfully, but these errors were encountered: