A Metamask fork with Infura removed and default networks editable
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Brad Decker 8f371e4f87
add eip-1559 fields to event schema (#11408)
3 years ago
.circleci Add logs for Google Chrome binary checksum verification (#11366) 3 years ago
.github Fix CLA Signature bot workflow (#11250) 3 years ago
.storybook Removing obsolete client-side transaction metrics events (#11329) 3 years ago
app add eip-1559 fields to event schema (#11408) 3 years ago
development Implements the new EIP1559 UI components (#11384) 3 years ago
docs remove matomo and route to segment (#9646) 4 years ago
lavamoat/node cleanup conflicts 3 years ago
patches Enable Chrome E2E logs (#11295) 3 years ago
shared update txParams normalization and validation. (#11406) 3 years ago
test Removing obsolete client-side transaction metrics events (#11329) 3 years ago
ui add scroll function to jump to the top of screen (#11386) 3 years ago
.editorconfig Clean EditorConfig file 6 years ago
.eslintrc.js use jest for testing shared (#11334) 3 years ago
.gitattributes Use Infura v3 API (#9368) 4 years ago
.gitignore remove the ui/app and ui/lib folders (#10911) 4 years ago
.metamaskrc.dist add segment implementation of metametrics (#9382) 4 years ago
.nvmrc Update to Node v14 (#9514) 4 years ago
.prettierignore Add jest-coverage/ to prettierignore (#10865) 4 years ago
.prettierrc.yml @metamask/eslint config@5.0.0 (#10358) 4 years ago
.yarnrc Add .yarnrc to disable scripts (#10354) 4 years ago
CHANGELOG.md cleanup conflicts 3 years ago
LICENSE Add new license (#9282) 4 years ago
README.md Fix community links in README (#11289) 3 years ago
babel.config.js @metamask/eslint config@5.0.0 (#10358) 4 years ago
jest.config.js fix jest tests to run ui tests (#11390) 3 years ago
jsconfig.json fix jsconfig woes (#11253) 3 years ago
nyc.config.js @metamask/eslint config@5.0.0 (#10358) 4 years ago
package.json Merge remote-tracking branch 'origin/develop' into master-sync 3 years ago
stylelint.config.js @metamask/eslint-config*@6.0.0 (#10858) 4 years ago
yarn.lock Update controllers with conversionRate change with minimal required changes in extension (#11361) 3 years ago

README.md

MetaMask Browser Extension

Hey! We are hiring JavaScript Engineers! Apply here!

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

For general questions, feature requests, or developer questions, visit our Community Forum.

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 14
    • If you are using nvm (recommended) running nvm use will automatically choose the right node version for you.
  • Install Yarn
  • Install dependencies: yarn setup (not the usual install command)
  • 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.

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

Contributing

Development builds

To start a development build (e.g. with logging and file watching) run yarn start.

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)

Running Unit Tests and Linting

Run unit tests and the linter with yarn test.

To run just unit tests, run yarn test:unit. To run unit tests continuously with a file watcher, run yarn watch.

You can run the linter by itself with yarn lint, and you can automatically fix some lint problems with yarn lint:fix. You can also run these two commands just on your local changes to save time with yarn lint:changed and yarn lint:changed:fix respectively.

Running E2E Tests

Our e2e test suite can be run on either Firefox or Chrome. In either case, start by creating a test build by running yarn build:test.

Firefox e2e tests can be run with yarn test:e2e:firefox.

Chrome e2e tests can be run with yarn test:e2e:chrome, but they will only work if you have Chrome v79 installed. Update the chromedriver package to a version matching your local Chrome installation to run e2e tests on newer Chrome versions.

Changing dependencies

Whenever you change dependencies (adding, removing, or updating, either in package.json or yarn.lock), there are various files that must be kept up-to-date.

  • yarn.lock:
    • Run yarn setup again after your changes to ensure yarn.lock has been properly updated.
  • The allow-scripts configuration in package.json
    • Run yarn allow-scripts auto to update the allow-scripts configuration automatically. This config determines whether the package's install/postinstall scripts are allowed to run. Review each new package to determine whether the install script needs to run or not, testing if necessary.
    • Unfortunately, yarn allow-scripts auto will behave inconsistently on different platforms. macOS and Windows users may see extraneous changes relating to optional dependencies.
  • The LavaMoat auto-generated policy in lavamoat/node/policy.json
    • Run yarn lavamoat:auto to re-generate this policy file. Review the changes to determine whether the access granted to each package seems appropriate.
    • Unfortunately, yarn lavamoat:auto will behave inconsistently on different platforms. macOS and Windows users may see extraneous changes relating to optional dependencies.

Architecture

Architecture Diagram

Development

yarn
yarn start

Build for Publishing

yarn dist

Other Docs