Back to your queue due to test failures.

The config is needed down the road is just saying nothing at all.

You say that it differs from the original by passing a config, but provide no reason as to why. It doesn't looks like to me that this difference is justified.

In D8899#204315, @PiRK wrote:

I added a few tests, but now I 'm no longer sure that all situations described in the PR are possible. I don't know how to reasonably generate a CTransaction whose outputs would add up to an int64 overflow without any single one of the outputs being larger than MAX_MONEY.
It would require 439208192231 outputs.

I know there isn't int he original code, but there should really be tests cases for this.

Address comments

rebase

The requested change differ from the existing code style for a benefit that is at best elusive.

Remove debug logs

Fix node version message (relay and extra entropy were reverted)

Updated package-lock and rebase

In D8838#202946, @josephroyking wrote:

I'm able to get npm install to work here with node v15.3.0 or v15.4.0 and npm v7.0.15 (but package-lock.json is different)

npm v7.3.0 runs into dependency issue without --legacy-peer-deps

What version of node and npm did you use for this diff?

Could you please run

cd cashtab/web
rm -rf node_modules
rm package-lock-json
npm i

and submit?

Check build failure

If you need --legacy-peer-deps you have regressed something.

1/ I cannot reproduce, npm start works just fine on master.
2/ Knowing what the error is would help assert if the solution is appropriate.

Removed @testing-library/react-hooks because it has conflicts, and it doesn't seems liek it is used. It would be good to double check, because everything seems busted around here.

rebase

rebase

rebase

rebase

rebase

Stay on webpack 4

Remove useless prettierignore

Remove typescript-eslint modules, as we don't use typescript