cb12cb8f5a
Support has been restored for Chromium v78. Previously the extension would crash upon startup. The main incompatibility was the use of ES2020 operators (the optional chain and nullish coalesce operators) in the libraries `@ethereumjs/util` and `superstruct`. This was resolved by transpiling those libraries. After fixing that, the extension no longer crashed but the UI refused to connect. This was because the UI process was not being identified as an internal process, because the code responsible for checking that was relying on the `origin` property of `MessageSender` [1] which wasn't added until Chromium v80. The check has been updated to use the `url` property instead, which existed in older versions of Chrome. Lastly, the content security policy was updated to include the default content security policy alongside the intended modification. Newer versions of Chrome will merge the configired CSP with the default, but older versions required it to be explicitly specified. This should not result in any functional change. [1]: https://developer.chrome.com/docs/extensions/reference/runtime/#type-MessageSender |
||
|---|---|---|
| .. | ||
| transforms | ||
| config.js | ||
| constants.js | ||
| display.js | ||
| etc.js | ||
| index.js | ||
| manifest.js | ||
| README.md | ||
| sass-compiler.js | ||
| scripts.js | ||
| static.js | ||
| styles.js | ||
| task.js | ||
| utils.js | ||
The MetaMask Build System
tl;dr
yarn distfor prod,yarn startfor local development. Add--build-type flaskto build Flask, our canary distribution with more experimental features.
This directory contains the MetaMask build system, which is used to build the MetaMask Extension such that it can be used in a supported browser.
From the repository root, the build system entry file is located at ./development/build/index.js.
Several package scripts invoke the build system.
For example, yarn start creates a watched development build, and yarn dist creates a production build.
Some of these scripts applies lavamoat to the build system, and some do not.
For local development, building without lavamoat is faster and therefore preferable.
The build system is not a full-featured CLI, but rather a script that expects some command line arguments and environment variables. For instructions regarding environment variables, see the main repository readme.
Generally speaking, the build system consists of gulp tasks that either manipulate static assets or bundle source files using Browserify.
Production-ready zip files are written to the ./builds directory, while "unpacked" extension builds
are written to the ./dist directory.
Our JavaScript source files are transformed using Babel, specifically using
the babelify Browserify transform.
Source file bundling tasks are implemented in the ./development/build/scripts.js.
Locally implemented Browserify transforms, some of which affect how we write JavaScript, are listed and documented here.
Usage
See node ./development/build/index.js --help