This is fixed in 1.5.0. So the used web3 version should be updated soon.
This is fixed in 1.5.0.
So the used web3 version should be updated soon.