-
Notifications
You must be signed in to change notification settings - Fork 480
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
'@web3-onboard/torus' - NextJS 12 Loads in dev, but not in Vercel production #1848
Comments
Hi @Seroxdesign you may want to give the web3auth/torus docs a look here: https://web3auth.io/docs/examples?product=Plug+and+Play&sdk=Plug+and+Play+Web+Modal+SDK for some ideas. |
@Seroxdesign is this still an issue? |
Still an issue @Adamj1232, unfortunately we set this aside for now until this gets resolved. |
@Seroxdesign did you happen to look into the web3auth/torus docs for resolution? |
I did, I practically scoured everything I could find, including docs, github issues etc.. could be something to do with our complex tech stack |
In the next.config.js file try setting swcMinify to false |
@Seroxdesign we recently updated the @web3-onboard/torus package- will you update and let me know if you're still experiencing this issue? |
@Seroxdesign closing for now- feel free to reopen if you test the updated package and still experience the same issue (or please post if you found a solution previously). Thanks! |
Current Behavior
ISSUE
the torus module doesn't' work in Vercel production, but it works in development.
I have set up webpack, babel and installed all packages following the documentation:
https://onboard.blocknative.com/docs/wallets/torus
The package loads, and is available in the wallets array, but doesn't show up/work.
Expected Behavior
It should work as it works in development
Steps To Reproduce
import torusModule from '@web3-onboard/torus'
What package is effected by this issue?
@web3-onboard/torus
Is this a build or a runtime issue?
Runtime
Package Version
2.20.04
Node Version
Node 16
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
Relevant log output
Anything else?
No response
Sanity Check
The text was updated successfully, but these errors were encountered: