-
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
Consider replacing web3 for ethers.js #5
Comments
I'm all for moving towards ethers.js as long as we provide compatibility with people using web3 too. Projects already on Truffle should be able to migrate their tests suites with relatively low friction. |
Agree! I created #6 to discuss how to approach that. |
I found this web3 compatibility layer already implemented by the author of ethers.js https://github.com/ethers-io/ethers-web3-bridge 🙌🏻 |
We are migrating to ethers.js |
* Add getters for block.gaslimit and gasleft() values to test contract * Remove duplicated deployContract function in evm module tests * Create a failing test showing that gasleft() value is affected * Make _runTx method not change the tx gasLimit value * Fix lint
* created VibrantCommunityBlock component * Move color to theme, Add secondary button styles for CTA * Fix lint errors
Most of buidler's instability comes from using web3, and in particular web3-provider-engine.
We should consider using ethers.js instead. We could create an ethers-powered web3 shim if necessary.
I haven't had enough time to experiment on this yet, but I think it's a promising idea. Still, it would be a big change, so I'll like to get some feedback about it.
The text was updated successfully, but these errors were encountered: