CI Warnings

**Describe the bug**

Warnings on latest `develop` https://github.com/bitshares/bitshares-ui/commit/0ac6c931a9764bc87ac9c7c5aeb564962d0352f3 (see https://ci.appveyor.com/project/svk31/bitshares-ui/builds/41990657)
> yarn install v1.21.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
warning sha.js@2.4.11: Invalid bin entry for "sha.js" (in "sha.js").
warning lzma@2.1.6: Invalid bin entry for "lzma.js" (in "lzma").
info fsevents@1.2.13: The platform "win32" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
info dmg-license@1.0.10: The platform "win32" is incompatible with this module.
info "dmg-license@1.0.10" is an optional dependency and failed compatibility check. Excluding it from installation.
info iconv-corefoundation@1.1.7: The platform "win32" is incompatible with this module.
info "iconv-corefoundation@1.1.7" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@2.3.2: The platform "win32" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " > bitshares-report@2.0.0" has incorrect peer dependency "bitsharesjs@^1.8.0".
warning " > react-json-inspector@7.1.1" has incorrect peer dependency "react@^15.0.0".
warning " > react-tooltip@3.11.6" has incorrect peer dependency "react@>=^16.0.0".
warning " > react-tooltip@3.11.6" has incorrect peer dependency "react-dom@>=^16.0.0".
warning " > react-sticky-table@1.2.0" has incorrect peer dependency "react@^15.0.0".
warning " > react-sticky-table@1.2.0" has incorrect peer dependency "react-dom@ ^15.0.0".
[5/5] Building fresh packages...

> cross-env NODE_ENV=production webpack --env prod --env electron --env hash
(node:2468) Warning: Accessing non-existent property 'cat' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2468) Warning: Accessing non-existent property 'cd' of module exports inside circular dependency
...
(node:2468) Warning: Accessing non-existent property 'uniq' of module exports inside circular dependency
(node:2468) Warning: Accessing non-existent property 'which' of module exports inside circular dependency

and more.

Start by rerunning yarn install and the webpack production build shown in the issue, then compare the output with the linked AppVeyor build. Review package.json and the dependency warnings to determine which warnings are actionable and which are expected platform messages. Done means the agreed CI warnings are removed or documented without breaking the build.

Written by the indexing model from the issue text.