Skip to content
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

[email protected] no support react 19 #4880

Open
seewindcn opened this issue Feb 27, 2025 · 6 comments
Open

[email protected] no support react 19 #4880

seewindcn opened this issue Feb 27, 2025 · 6 comments

Comments

@seewindcn
Copy link
Contributor

Describe the bug
A clear and concise description of what the bug is.
[email protected]

 "peerDependencies": {
   "react": "^15.3.0 || 16 || 17 || 18"
 },

DebounceInput component use this library.

error messages:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: reflex@undefined
npm error Found: [email protected]
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@"^15.3.0 || 16 || 17 || 18" from [email protected]
npm error node_modules/react-debounce-input
npm error   react-debounce-input@"3.3.0" 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.
Copy link

linear bot commented Feb 27, 2025

@masenf
Copy link
Collaborator

masenf commented Feb 27, 2025

Interesting. Although the package only claims support for React 18, the package does seem to work fine with React 19 and our default installer, bun doesn't seem to error out with this peer dependency issue.

Is there a reason why you're using npm to install? What platform are you on?

@masenf
Copy link
Collaborator

masenf commented Feb 27, 2025

I filed an issue in the upstream package nkbt/react-debounce-input#161 not dissimilar to previous issues requesting the same for React 17 and 18 over the years. Hopefully we can get a new version released which doesn't have this issue. In the mean time, if you're able to install deps with bun then things should still be working.

@seewindcn
Copy link
Contributor Author

seewindcn commented Feb 28, 2025

in China, reflex use bun with registry = "https://r.cnpmjs.org", this will raise some errors:

bun install v1.2.0 (b0c5a765)
warn: CERT_HAS_EXPIRED downloading tarball [email protected]

warn: incorrect peer dependency "[email protected]"

warn: incorrect peer dependency "[email protected]"

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

error: CERT_HAS_EXPIRED downloading tarball [email protected]

then will fallback to use npm.
my system is windows.

@alexlausz
Copy link

alexlausz commented Feb 28, 2025

I'm a user from China. I encountered the same problem when running the Reflex project using npm in the Ubuntu 24.04 environment of Windows 11 WSL2.

Image

Besides, I'll explain why npm should be used:
Although I set up a network proxy in WSL2, after a certain version of 0.6.6, when running the Reflex project, the default Bun compilation step would get stuck for dozens of minutes. Then I tried npm and added the following configurations:
REFLEX_USE_NPM = 1
NPM_CONFIG_REGISTRY = http://registry.npmmirror.com/
However, Reflex still used Bun (perhaps because my system is Ubuntu instead of Windows?). Later, I solved the problem with the help of Windsurf. It modified the get_install_package_manager method in the utils/prerequisites.py file and gave priority to the setting of environment.REFLEX_USE_NPM.
Since then, every time I upgrade the version of Reflex, I have to repeatedly modify the get_install_package_manager method to use npm.

@weihuan
Copy link

weihuan commented Mar 1, 2025

Yes, I encountered the same issue while upgrading to 0.7.1. I am using Windows 11 and NPM. Could you please provide a patch for 0.7.1 to resolve this problem? For now, I have no choice but to revert back to 0.7.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants