13a1e63184
Previously Chrome would ignore an attempt to navigate to a restricted URL like an extension page that is not web accessible. In a recent Chrome update, this has changed. Now it does perform the navigation, but to an error page that explains that the request was invalid. The last assertion, responsible for checking that the warning page is still shown, has been removed. The test still ensures the main wallet UI is not loaded, that assertion was not needed. |
||
---|---|---|
.circleci | ||
.github | ||
.storybook | ||
app | ||
development | ||
docs | ||
lavamoat | ||
patches | ||
shared | ||
test | ||
ui | ||
.depcheckrc.yml | ||
.editorconfig | ||
.eslintrc.babel.js | ||
.eslintrc.base.js | ||
.eslintrc.js | ||
.eslintrc.jsdoc.js | ||
.eslintrc.node.js | ||
.eslintrc.typescript-compat.js | ||
.gitattributes | ||
.gitignore | ||
.iyarc | ||
.metamaskrc.dist | ||
.mocharc.js | ||
.nvmrc | ||
.prettierignore | ||
.prettierrc.yml | ||
.yarnrc | ||
babel.config.js | ||
CHANGELOG.md | ||
crowdin.yml | ||
jest.config.js | ||
jest.stories.config.js | ||
LICENSE | ||
nyc.config.js | ||
package.json | ||
README.md | ||
stylelint.config.js | ||
tsconfig.json | ||
yarn.lock |
MetaMask Browser Extension
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.
- If you are using nvm (recommended) running
- 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, see Developing on MetaMask.
- Replace the
- Build the project to the
./dist/
folder withyarn dist
.
Uncompressed builds can be found in /dist
, compressed builds can be found in /builds
once they're built.
See the build system readme for build system usage information.
Contributing
Development builds
To start a development build (e.g. with logging and file watching) run yarn start
.
React and Redux DevTools
To start the React DevTools, run yarn devtools:react
with a development build installed in a browser. This will open in a separate window; no browser extension is required.
To start the Redux DevTools Extension:
- Install the package
remotedev-server
globally (e.g.yarn global add remotedev-server
) - Install the Redux Devtools extension.
- Open the Redux DevTools extension and check the "Use custom (local) server" checkbox in the Remote DevTools Settings, using the default server configuration (host
localhost
, port8000
, secure connection checkbox unchecked).
Then run the command yarn devtools:redux
with a development build installed in a browser. This will enable you to use the Redux DevTools extension to inspect MetaMask.
To create a development build and run both of these tools simultaneously, run yarn start:dev
.
Test Dapp
This test site can be used to execute different user flows.
Running Unit Tests and Linting
Run unit tests and the linter with yarn test
. To run just unit tests, run yarn test:unit
.
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
. Thechromedriver
package major version must match the major version of your local Chrome installation. If they don't match, update whichever is behind before running Chrome e2e tests. -
Single e2e tests can be run with
yarn test:e2e:single test/e2e/tests/TEST_NAME.spec.js
along with the options below.
--browser Set the browser used; either 'chrome' or 'firefox'.
--leave-running Leaves the browser running after a test fails, along with anything else
that the test used (ganache, the test dapp, etc.).
--retries Set how many times the test should be retried upon failure. Default is 0.
An example for running account-details
testcase with chrome and leaving the browser open would be:
yarn test:e2e:single test/e2e/tests/account-details.spec.js --browser=chrome --leave-running
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 ensureyarn.lock
has been properly updated. - Run
yarn yarn-deduplicate
to remove duplicate dependencies from the lockfile.
- Run
- The
allow-scripts
configuration inpackage.json
- Run
yarn allow-scripts auto
to update theallow-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.
- Run
- The LavaMoat policy files. The tl;dr is to run
yarn lavamoat:auto
to update these files, but there can be devils in the details. Continue reading for more information.- There are two sets of LavaMoat policy files:
- The production LavaMoat policy files (
lavamoat/browserify/*/policy.json
), which are re-generated usingyarn lavamoat:background:auto
.- These should be regenerated whenever the production dependencies for the background change.
- The build system LavaMoat policy file (
lavamoat/build-system/policy.json
), which is re-generated usingyarn lavamoat:build:auto
.- This should be regenerated whenever the dependencies used by the build system itself change.
- The production LavaMoat policy files (
- Whenever you regenerate a 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. - Keep in mind that any kind of dynamic import or dynamic use of globals may elude LavaMoat's static analysis. Refer to the LavaMoat documentation or ask for help if you run into any issues.
- There are two sets of LavaMoat policy files: