Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Metamask Extension | 10,634 | 3 | 16 hours ago | 2 | June 10, 2022 | 1,793 | other | JavaScript | ||
:globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites | ||||||||||
App Monorepo | 1,578 | 2 days ago | 30 | apache-2.0 | TypeScript | |||||
Secure, open source and community driven crypto wallet runs on all platforms and trusted by millions. | ||||||||||
Mycrypto | 1,248 | 9 months ago | 35 | mit | TypeScript | |||||
MyCrypto is an open-source tool that allows you to manage your Ethereum accounts privately and securely. Developed by and for the community since 2015, we’re focused on building awesome products that put the power in people’s hands. | ||||||||||
Blockchain Wallet V4 Frontend | 677 | a day ago | 39 | agpl-3.0 | TypeScript | |||||
Blockchain.com's open source, non-custodial Wallet | ||||||||||
Drizzle Legacy | 519 | 126 | 8 | 4 years ago | 33 | August 12, 2019 | 4 | mit | JavaScript | |
Reactive Ethereum datastore for dapp UIs. | ||||||||||
Augur Ui | 412 | 1 | 1 | 3 years ago | 120 | March 30, 2020 | 3 | mit | JavaScript | |
Augur UI | ||||||||||
React Native Redux Crypto Tracker | 364 | 6 years ago | 1 | mit | JavaScript | |||||
💎 Learn how to build a Redux + React Native cryptocurrency app | ||||||||||
React Ethereum Dapp Example | 363 | 6 years ago | 2 | mit | JavaScript | |||||
A starter boilerplate for an Ethereum dapp using web3.js v1.0, truffle, react, and parity | ||||||||||
React Auth Box | 171 | 3 years ago | 23 | mit | JavaScript | |||||
Truffle, Webpack, React, Redux boilerplate with routing and authentication via a smart contract. | ||||||||||
Alchemy | 137 | a year ago | 49 | gpl-3.0 | TypeScript | |||||
An app for collaborative networks (DAOs), based on the DAO stack. |
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.
nvm use
will automatically choose the right node version for you..metamaskrc.dist
within the root and rename it to .metamaskrc
INFURA_PROJECT_ID
value with your own personal Infura Project ID.SEGMENT_WRITE_KEY
Segment write key, see Developing on MetaMask - Segment.SENTRY_DSN
Sentry Dsn, see Developing on MetaMask - Sentry.PASSWORD
value with your development wallet password to avoid entering it each time you open the app../dist/
folder with yarn dist
.
yarn start
to run dev mode.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.
To get quick feedback from our shared code quality fitness functions before committing the code, you can install our git hooks with Husky.
$ yarn githooks:install
You can read more about them in our testing documentation.
To start a development build (e.g. with logging and file watching) run yarn start
.
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:
remotedev-server
globally (e.g. yarn global add remotedev-server
)localhost
, port 8000
, 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
.
This test site can be used to execute different user flows.
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.
For Jest debugging guide using Node.js, see docs/tests/jest.md.
Our e2e test suite can be run on either Firefox or Chrome.
yarn build:test
to create a test build.yarn test:e2e:firefox
.yarn test:e2e:chrome
. The chromedriver
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.These test scripts all support additional options, which might be helpful for debugging. Run the script with the flag --help
to see all options.
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'.
[string] [choices: "chrome", "firefox"]
--debug Run tests in debug mode, logging each driver interaction
[boolean] [default: false]
--retries Set how many times the test should be retried upon failure.
[number] [default: 0]
--leave-running Leaves the browser running after a test fails, along with
anything else that the test used (ganache, the test dapp,
etc.) [boolean] [default: false]
For example, to run the account-details
tests using Chrome, with debug logging and with the browser set to remain open upon failure, you would use:
yarn test:e2e:single test/e2e/tests/account-details.spec.js --browser=chrome --debug --leave-running
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
:
yarn
again after your changes to ensure yarn.lock
has been properly updated.yarn lint:lockfile:dedupe:fix
to remove duplicate dependencies from the lockfile.allow-scripts
configuration in package.json
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.yarn allow-scripts auto
will behave inconsistently on different platforms. macOS and Windows users may see extraneous changes relating to optional dependencies.@metamaskbot update-policies
to ask the MetaMask bot to automatically update the policies for you.yarn lavamoat:auto
to update these files, but there can be devils in the details:
lavamoat/browserify/*/policy.json
), which are re-generated using yarn lavamoat:background:auto
. Add --help
for usage.
lavamoat/build-system/policy.json
), which is re-generated using yarn lavamoat:build:auto
.
yarn lavamoat:auto
will behave inconsistently on different platforms.
macOS and Windows users may see extraneous changes relating to optional dependencies.rm -rf node_modules/ && yarn && yarn lavamoat:auto