Upgrade to web3 1.0 once released

[LogvinovLeon]

No description provided.

[Esqarrouth]

Whats this issue about?

[LogvinovLeon]

The issue is about us planning to upgrade to using web3@1.0 internally as soon as it's production quality. For now it's still in beta and there was no stable release. Also types are sometimes wrong and incomplete

[fabioberger]

It's looking like we might never do this. Ethers.js is moving to TypeScript and supports ABIv2 and other features we want. In addition, we are using fewer and fewer Web3.js endpoints, to the point where it would be quite easy for us to drop it entirely.

[BennyTheDev]

...let's say you skip web3 altogether, will 0x still be able to use metamask (or its successor) as provider?

Thanks!

[fabioberger]

@crosstec we've removed web3 entirely from our codebase but still use the Provider interface defined by it. We are therefore still compliant with Metamask.

[BennyTheDev]

thanks!