-
Notifications
You must be signed in to change notification settings - Fork 1.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
Web3Connect modal missing images #12
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 50.0 DAI (50.0 USD @ $1.0/DAI) attached to it as part of the WalletConnect fund.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 1 week, 6 days from now. 1) skyge has started work. I ever tried to change my own image when I connect to metamask. Learn more on the Gitcoin Issue Details page. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 1 week, 4 days from now. 1) skyge has started work. I ever tried to change my own image when I connect to metamask. Learn more on the Gitcoin Issue Details page. 2) skyge has started work. I ever tried to change my own image when I connect to metamask. Learn more on the Gitcoin Issue Details page. 3) devaman has started work. Will take a keen look on how the webpack is working for this project. Learn more on the Gitcoin Issue Details page. |
⚡️ A tip worth 50.00000 DAI (50.0 USD @ $1.0/DAI) has been granted to @devaman for this issue from @pedrouid. ⚡️ Nice work @devaman! Your tip has automatically been deposited in the ETH address we have on file.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This Bounty has been completed. Additional Tips for this Bounty:
|
The Web3Connect modal is very much a work in progress but I need someone to debug why the images are not being imported to NPM or are not being packaged properly with Webpack.
Expected Behavior
Actual Behavior
The text was updated successfully, but these errors were encountered: