-
Notifications
You must be signed in to change notification settings - Fork 516
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
global is not defined when trying to connect with wallet connect (Nuxt3 + Vite) #1675
Comments
@SpiritusDeos have a look at the issue resolved here for Vite as it may provide a solution. Let me know if this works for you - #1568 (comment) |
Just look into your resolved issue - looks to work with svelte but in Nuxt 3 you don't deal with any |
Didn't success to make it works until now, even with the issue linked... @Adamj1232, do you have any proper config working with Vite/Nuxt 3 ? |
@SpiritusDeos we haven't had a chance to look into this yet but will update here when we do. |
Hey @Adamj1232 - still no news ? |
@SpiritusDeos we have been a little buried with new projects and features to get to this. We always welcome PR. You may also want to check with the walletconnect team as whatever settings to get their packages working in this environment would extend here - give this a look and let me know if it happens to work for you - WalletConnect/walletconnect-monorepo#655 |
I was able to solve this issue by adding the following to my vite config.
Hope this helps 😄 |
@SpiritusDeos please let us know if @ricky-barnett solution above works for you! We will add this to our documentation if so! |
Current Behavior
Can't open wallet connect with the neversion of web3-onboard in local (other environment looks to work correctly)
Expected Behavior
To be able to open web3-onboard with wallet connect
Steps To Reproduce
Install Nuxt 3.4.3 project + Vite with this configuration, and you can't connect using wallet connect
What package is effected by this issue?
@web3-onboard/vue
Is this a build or a runtime issue?
Runtime
Package Version
2.7.0
Node Version
16.14
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Anything else?
No response
Sanity Check
The text was updated successfully, but these errors were encountered: