m/metamask-extension
1
0
Fork 0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-11-29 23:58:06 +01:00
Code
1482cd1c96
metamask-extension/development/build
History
David Walsh 5b1b5dc03b
NFTs: Remove feature flag for release (#17401) 
* NFTs: Remove feature flag for release

* Update security tab jest test

* Fix broken test

* Update snapshot

* Update test

* Fix test

* Remove last usages of flag

* Update CI jobs

* Fix jest tests
2023-03-13 14:29:37 -05:00
..
transforms [MMI] Adds mmi build type + manifest files and images (#17842) 2023-03-01 09:38:15 +00:00
config.js NFTs: Remove feature flag for release (#17401) 2023-03-13 14:29:37 -05:00
constants.js Add validation to production build script (#15468) 2022-08-19 15:46:18 -02:30
display.js
etc.js
index.js Turn off LM scuttling feature for dev builds (#17771) 2023-02-28 13:29:24 +02:00
manifest.js remove exclusions for mismatched object jsdoc type casing (#15351) 2022-07-27 08:28:05 -05:00
README.md
sass-compiler.js
scripts.js NFTs: Remove feature flag for release (#17401) 2023-03-13 14:29:37 -05:00
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 Fix build script errors (#15493) 2022-08-06 03:33:35 -04:00
utils.js feat(17494): beta build trigger in release branch and cleanup (#17749) 2023-03-04 12:51:04 +00: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