-
Notifications
You must be signed in to change notification settings - Fork 13
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
Set up wagmi + rainbowkit. #2
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…ates/react-dom for react 18/next13
Following these threads to fix issue w/ tanstack.TanStack/query#4933 Here is the error in a sandbox:Here is a sandbox w/ the issue fixed:TanStack/query#4933 (comment) Here is another outline of the supposed steps, working for a next13 app:https://blog.gogrow.dev/setting-up-react-query-in-your-next-js-13-app-e8edea0d20cc Here is the tanstack pointing to a PR by FB to update react :
Release name: [18.3.0-canary-1fdacbefd-20230630]Release commit: vercel/next.js@1ae3f42 Still getting issues... resuming tomorrow. |
…Edge runtime was the crux.
Tested, still seems to be working. Noticed an issue with chat history not being saved, probably a config issue w/ supabase, will dig later. Great work @kdetry |
This ticket is dependent on if we want to try to use this stack.
Fixes #1
Problem:
unstable_batchedUpdates
Outline
Further technical details
Please see comments below
Current Blocker
(Problem 2) - I believe latest react release should address the requirements, however I do not seem to be getting it resolved.
Alternative candidates: