Inscreva-se aqui !
Ei! Estamos contratando engenheiros de JavaScript!Você pode encontrar a versão mais recente do MetaMask em nosso site oficial . Para obter ajuda sobre como usar o MetaMask, visite nosso site de suporte ao usuário .
Para perguntas gerais , solicitações de recursos ou perguntas de desenvolvedor , visite nosso Fórum da comunidade .
MetaMask oferece suporte a navegadores baseados em Firefox, Google Chrome e Chromium. Recomendamos usar a versão mais recente do navegador disponível.
Para notícias atualizadas, siga nossas páginas do Twitter ou do Medium .
Para saber como desenvolver aplicativos compatíveis com MetaMask, visite nosso Developer Docs .
Para saber como contribuir com o projeto MetaMask em si, visite nossos documentos internos .
Construindo localmente
- Instale o Node.js versão 14
- Se você estiver usando nvm (recomendado), a execução
nvm use
escolherá automaticamente a versão de nó certa para você.
- Se você estiver usando nvm (recomendado), a execução
- Instale o Yarn
- Instale dependências:
yarn setup
(não o comando de instalação usual) - Copie o
.metamaskrc.dist
arquivo para.metamaskrc
- Substitua o
INFURA_PROJECT_ID
valor pelo seu próprio ID do Projeto Infura pessoal . - Se estiver depurando MetaMetrics, você precisará adicionar um valor para a
SEGMENT_WRITE_KEY
chave de gravação do segmento .
- Substitua o
- Compile o projeto para a
./dist/
pasta comyarn dist
.
As compilações não compactadas podem ser encontradas em /dist
, as compilações compactadas podem ser encontradas /builds
assim que forem criadas.
Contribuindo
Compilações de desenvolvimento
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
, port8000
, secure connection checkbox unchecked)
- You will also need to check the "Use custom (local) server" checkbox in the Remote DevTools Settings, using the default server configuration (host
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 ensureyarn.lock
has been properly updated.
- 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 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.
- Run
Architecture
Development
yarn yarn start
Build for Publishing
yarn dist