-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[bug] Can't import the named export 'useSyncExternalStore' from non EcmaScript module #398
Comments
Which version of react-query is wagmi using? This should be fixed with v4.0.0-beta.7: https://github.com/tannerlinsley/react-query/releases/tag/v4.0.0-beta.7 |
@TkDodo |
interesting - but we also switched to a different bundling strategy in beta.6: maybe this has something to do with it? If you can try out if things still work with |
@TkDodo will do. Thanks for the tip! @carlomigueldy what bundler are you using? |
Hello folks @tmm @TkDodo sorry for getting back late here, just got so busy and flooded with some priorities at hand.
In our codebase we are currently using Create-React-App (CRA) |
Hmm I am gonna check it out! |
Sounds good! (Let's also not tag TkDodo here anymore until we have something concrete. I'm sure he's a busy guy.) |
hi @carlomigueldy , my project is also using CRA and hitting the same issue. were you able to find a fix or workaround? |
@just-toby What version of CRA? |
@tmm we were using |
for the record, we're working around this issue using react-app-rewired for the time being, at least until we migrate away from the old CRA version |
+1- we're also using |
Same error with CRA using I've not dabbled with webpack much, someone mind explaining the Edit: jk, Just looked at facebook/create-react-app#11756 |
up |
This appears to be an issue with Closing this as wagmi is only supporting |
can confirm, updating to |
This is also happening with |
@eenagy do you have a minimal reproducible example for Next.js? |
|
|
There's any workaround for this if I want to keep using cra4? |
please have a look at https://github.com/tannerlinsley/react-query/releases/tag/v4.0.0-beta.17 where we've hopefully fixed the upstream issue. |
This issue has been locked since it has been closed for more than 14 days. If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest wagmi version. If you have any other comments you can create a new discussion. |
Is there an existing issue for this?
Package Version
0.3.1
Current Behavior
I have no clue where it originates, I only migrated from ^0.1.3 to ^0.3.1 then suddenly it starts becoming an issue
Expected Behavior
Should not throw this exception
Steps To Reproduce
Create a new project and use multiple hooks and specifically use version
^0.1.3
then migrate to^0.3.1
so you'll have to change most hooks since it returns single objectLink to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
The text was updated successfully, but these errors were encountered: