Using the latest OpenZeppelin NetworkJS ( https://github.com/OpenZeppelin/openzeppelin-network.js/tree/master ) useWeb3Injected() doesn’t catch the situation when no web3 provider is available and instead throws an error if MetaMask (or other injected provider) is not found. This error crashes the us…

Hi @Dennison , There is now a Pull Request to change this behavior: https://github.com/OpenZeppelin/openzeppelin-network.js/pull/24

Hey @Dennison . It always pleasing to get some feedback from you! You are right that network.js doesn’t catch A web3 provider is not attached to a window. error. This is by design because it needs web3 provider to operate. This can be easily prevented by checking windows.ethereum field before creati…

Hey @Dennison . After some considerations we decided to support not throwing errors . Enjoy!

OpenZeppelin Networkjs throws error with no provider

Archive SDK

Topic		Replies	Views
The future of OpenZeppelin Network JS? SDK	4	850	January 9, 2020
Network.js Vanilla JavaScript boilerplate Support	4	770	April 27, 2020
Welcome a new frontend library OpenZeppelin Network.js Announcements	0	3612	July 25, 2019
Building an OpenZeppelin Network.js powered dapp from scratch General	2	546	October 29, 2019
Can you use OpenZeppelin Network.js with Ethers? SDK	9	1156	February 3, 2020

OpenZeppelin Networkjs throws error with no provider

Related topics