m/metamask-extension
1
0
Fork 0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-11-26 12:29:06 +01:00
Code
1626f22704
metamask-extension/development/build
History
Dan J Miller f89f96343b Fix mv3 beta build (#18690) 
* Build beta with mv3 enabled

* Ensure firefox manifest is an mv2 version

* Revert "Ensure firefox manifest is an mv2 version"

This reverts commit fed74792b0fec33c3a85f2229eb560559d37afe5.

* Only create beta builds for the chrome platform

* Stop linting firefox for beta
2023-04-26 14:04:29 -02:30
..
transforms [MMI] Adds mmi build type + manifest files and images (#17842) 2023-03-01 09:38:15 +00:00
config.js Remove mobile sync feature (#18692) 2023-04-20 14:29:30 -02:30
constants.js Add validation to production build script (#15468) 2022-08-19 15:46:18 -02:30
display.js
etc.js
index.js Fix mv3 beta build (#18690) 2023-04-26 14:04:29 -02:30
manifest.js Add more info to Extensions list (#18391) 2023-04-06 11:37:55 -07:00
README.md
sass-compiler.js
scripts.js Remove mobile sync feature (#18692) 2023-04-20 14:29:30 -02:30
static.js [MMI] Adds mmi build type + manifest files and images (#17842) 2023-03-01 09:38:15 +00:00
styles.js build: run scss pipelines synchronously (#16301) 2022-11-04 02:28:52 +00:00
task.js
utils.js Adds build type mmi (#18399) 2023-03-31 14:21:58 +01:00

README.md

The MetaMask Build System

tl;dr yarn dist for prod, yarn start for local development. Add --build-type flask to 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