Mark Stacey 5ee1291662 Prevent accidental use of globals (#8340) ... Previously all browser globals were allowed to be used anywhere by ESLint because we had set the `env` property to `browser` in the ESLint config. This has made it easy to accidentally use browser globals (e.g. #8338), so it has been removed. Instead we now have a short list of allowed globals. All browser globals are now accessed as properties on `window`. Unfortunately this change resulted in a few different confusing unit test errors, as some of our unit tests setup assumed that a particular global would be used via `window` or `global`. In particular, `window.fetch` didn't work correctly because it wasn't patched by the AbortController polyfill (only `global.fetch` was being patched). The `jsdom-global` package we were using complicated matters by setting all of the JSDOM `window` properties directly on `global`, overwriting the `AbortController` for example. The `helpers.js` test setup module has been simplified somewhat by removing `jsdom-global` and constructing the JSDOM instance manually. The JSDOM window is set on `window`, and a few properties are set on `global` as well as needed by various dependencies. `node-fetch` and the AbortController polyfill/patch now work as expected as well, though `fetch` is only available on `window` now.		2020-04-15 14:23:27 -03:00
..
common.util.js
common.util.test.js
confirm-tx.util.js
confirm-tx.util.test.js
conversion-util.js
conversion-util.test.js
conversions.util.js
fetch-with-cache.js
fetch-with-cache.test.js
formatters.js
gas-time-estimates.util.js
i18n-helper.js
i18n-helper.test.js
metametrics.util.js
switch-direction.js
token-util.js
transactions.util.js
transactions.util.test.js
util.js
util.test.js