Migrate away from web3-provider-engine
See original GitHub issueAccording to the maintainers, it looks like web3-provider-enginer is no longer actively maintained / no longer recommended (see readme)
I discovered this issue when trying tackling duplicate dependencies. They are using old versions of ethereumjs-util
and eth-sig-util
read more
I will open a PR in their repo to update those dependencies. In the meantime I thought I’d start the discussion for migrating away.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Truffle migrate does not run 2_deploy_contracts.js
However running truffle migrate --network rinkeby does only a partial migrate. It does not go on to migrate 2_deploy_contracts.js . $ truffle ...
Read more >ConsenSys/truffle - Gitter
I'm having a bit of a bespoke issue related to trufflesuite/truffle#650 - I'm deploying a private uniswap instance in a truffle migration.
Read more >Web3ProviderEngine does not support synchronous requests
I wanted to config my truffle-config.js with provider.When I run command "truffle migrate --network ...
Read more >Programming Project - Phase 1 - Ethereum Smart Contract ...
λ truffle migrate --network kovan Compiling your contracts. ... \Documents\repo\eth-heirloom\node_modules\@trufflesuite\web3-provider-engine\index.js:57:14 ...
Read more >MetaMask - Bountysource
I made an issue discuss if/how to migrate away from web3-provider-engine. Any help (comments, articles, etc.) would be greatly appreciated!
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll pledge 300 DAI right now to a bounty. Anyone else here care to join me?
If you guys are interested in building a replacement for web3-provider-engine, I’d love to help out.
This library is an important tool for building providers, but it’s very out-of-date and buggy. I use it in burner-core, and I’d love to swap it out for a nice, modern replacement.