-
Notifications
You must be signed in to change notification settings - Fork 27.3k
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-dom does not have correct exports when in client component and runtime experimental-edge #47057
Comments
some issue |
This is a problem with things like react-query, redux, etc. that expect ./cc @jxom this atm. breaks wagmi with next.js 13 & edge runtime. |
Please verify that your issue can be recreated with Why was this issue marked with the
|
^ Please verify with the stable App Router (no flag needed) and stable |
@leerob For me this still happens with the latest canary version, and latest versions for react-query:
I'll try to provide a reproducible repo soon |
Got a minimal reproducible repo: https://github.com/GabeDuarteM/nextjs-bug-unstable_batchedUpdates To get the error, just clone the repo and do a |
This should be fixed by facebook/react#27028 -- please feel free to open a new issue with a repro if you're still running into this problem! |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.1.0: Sun Oct 9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000 Binaries: Node: 16.15.0 npm: 8.5.5 Yarn: 1.22.18 pnpm: N/A Relevant packages: next: 13.2.3 eslint-config-next: 13.2.2 react: 18.2.0 react-dom: 18.2.0
{
__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED: [Getter],
createPortal: [Getter],
flushSync: [Getter],
preinit: [Getter],
preload: [Getter],
version: [Getter],
default: [Getter]
}
The text was updated successfully, but these errors were encountered: