A Metamask fork with Infura removed and default networks editable

Mark Stacey 6c637bba9c Fix `fetch-with-cache` handling of interwoven requests (#10079 ) A data race was introduced in #9919 when the old synchronous storage API was replaced with an async storage API. The problem arises when `fetchWithCache` is called a second time while it's still processing another call. In this case, the `cachedFetch` object can become stale while blocked waiting for a fetch response, and result in a cache being overwritten unintentionally. See this example (options omitted for simplicity, and assuming an empty initial cache): ``` await Promise.all([ fetchWithCache('https://metamask.io/foo'), fetchWithCache('https://metamask.io/bar'), ] ``` The order of events could be as follows: 1. Empty cache retrieved for `/foo` route 2. Empty cache retrieved for `/bar` route 3. Call made to `/foo` route 4. Call made to `/bar` route 5. `/foo` response is added to the empty cache object retrieved in step 1, then is saved in the cache. 6. `/bar` response is added to the empty cache object retrieved in step 2, then is saved in the cache. In step 6, the cache object saved would not contain the `/foo` response set in step 5. As a result, `/foo` would never be cached. This problem was resolved by embedding the URL being cached directly in the cache key. This prevents simultaneous responses from overwriting each others caches. Technically a data race still exists when handing simultaneous responses to the same route, but the result would be that the last call to finish would overwrite the previous. This seems acceptable.		4 years ago
.circleci	Cache dependencies (#10065 )	4 years ago
.github	@metamask/contract-metadata (#9968 )	4 years ago
.storybook	Update to `@storybook/*@6` (#9956 )	4 years ago
app	Add eth_getProof to safe methods (#10070 )	4 years ago
development	Disable console in contentscript (#10040 )	4 years ago
docs	remove matomo and route to segment (#9646 )	4 years ago
shared	Add web3 shim usage notification (#10039 )	4 years ago
test	Add approval controller (#9401 )	4 years ago
ui	Fix `fetch-with-cache` handling of interwoven requests (#10079 )	4 years ago
.editorconfig	Clean EditorConfig file	6 years ago
.eslintrc.js	Fix contentscript injection failure on Firefox 56 (#10034 )	4 years ago
.gitattributes	Use Infura v3 API (#9368 )	4 years ago
.gitignore	Remove coveralls (#10063 )	4 years ago
.metamaskrc.dist	add segment implementation of metametrics (#9382 )	4 years ago
.nvmrc	Bump Node version to 10.18 (#7925 )	5 years ago
.prettierignore	[RFC] add prettier to eslint (#8595 )	4 years ago
.prettierrc.yml	[RFC] add prettier to eslint (#8595 )	4 years ago
CHANGELOG.md	Display boolean values when signing typed data (#10048 )	4 years ago
LICENSE	Add new license (#9282 )	4 years ago
README.md	add segment implementation of metametrics (#9382 )	4 years ago
babel.config.js	Increase Chrome minimum version (#10019 )	4 years ago
nyc.config.js	Add permissions controller unit tests (#7969 )	5 years ago
package.json	Remove coveralls (#10063 )	4 years ago
stylelint.config.js	Move stylelint ignore patterns into config (#9391 )	4 years ago
yarn.lock	Bump ini from 1.3.5 to 1.3.7 (#10064 )	4 years ago

README.md

MetaMask Browser Extension

You can find the latest version of MetaMask on our official website. For help using MetaMask, visit our User Support Site.

MetaMask supports Firefox, Google Chrome, and Chromium-based browsers. We recommend using the latest available browser version.

For up to the minute news, follow our Twitter or Medium pages.

To learn how to develop MetaMask-compatible applications, visit our Developer Docs.

To learn how to contribute to the MetaMask project itself, visit our Internal Docs.

Building locally

Install Node.js version 10
- If you are using nvm (recommended) running nvm use will automatically choose the right node version for you.
Install Yarn
Install dependencies: yarn
Copy the .metamaskrc.dist file to .metamaskrc
- Replace the INFURA_PROJECT_ID value with your own personal Infura Project ID.
- If debugging MetaMetrics, you'll need to add a value for SEGMENT_WRITE_KEY Segment write key.
Build the project to the ./dist/ folder with yarn dist.
Optionally, to start a development build (e.g. with logging and file watching) run yarn start instead.
- To start the React DevTools and Redux DevTools Extension alongside the app, use yarn start:dev.
  - React DevTools will open in a separate window; no browser extension is required
  - Redux DevTools will need to be installed as a browser extension. Open the Redux Remote Devtools to access Redux state logs. This can be done by either right clicking within the web browser to bring up the context menu, expanding the Redux DevTools panel and clicking Open Remote DevTools OR clicking the Redux DevTools extension icon and clicking Open Remote DevTools.
    - You will also need to check the "Use custom (local) server" checkbox in the Remote DevTools Settings, using the default server configuration (host localhost, port 8000, secure connection checkbox unchecked)

Uncompressed builds can be found in /dist, compressed builds can be found in /builds once they're built.

Contributing

Running Tests

Run tests with yarn test.

You can also test with a continuously watching process, via yarn watch.

You can run the linter by itself with yarn lint.

Architecture

Development

yarn
yarn start

Build for Publishing

yarn dist