-
Notifications
You must be signed in to change notification settings - Fork 639
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 18 with react-composer@5.0.2 #870
Comments
Same warnings here. Narrowed it down to react-composer when installing drei. All fine until @react-three/drei at which point a warning is thrown about React 18 |
Getting the same issue, seems to be broken with React 18 :( |
Getting the same issue with React 18. |
looks like react-composer hasn't been touched in over 4 years, i'll start by making an issue. if it's not maintained any longer i have to fork it or add it to /helpers |
React Composer was just updated. Please let me know if there are still issues that can be resolved through updates to that library. |
Thank you for the fix.
{
"name": "drei-test",
"private": true,
"version": "0.0.0",
"scripts": {
"dev": "vite",
"build": "tsc && vite build",
"preview": "vite preview"
},
"dependencies": {
"@react-three/drei": "^9.6.0",
"@react-three/fiber": "^8.0.12",
"react": "^18.0.0",
"react-dom": "^18.0.0",
"three": "^0.140.0"
},
"devDependencies": {
"@types/react": "^18.0.0",
"@types/react-dom": "^18.0.0",
"@types/three": "^0.139.0",
"@vitejs/plugin-react": "^1.3.0",
"typescript": "^4.6.3",
"vite": "^2.9.5"
}
} |
seems unrelated though, i think we can close this issue then. just needs an update for nanoid. could someone do the pr? |
As stated in the error message, there seems to be no need to install @types/nanoid in the first place. |
I dropped nanoid in #901 for other reasons, peer deps should be fine now. |
What is your question:
I am getting an error when installing react-three/drei
I can't tell if this is because of react-composer, or react-three/xr ( I have installed react-three/xr )
The text was updated successfully, but these errors were encountered: