From f9fb3027402bcff4d611709093508b8402ff4d3b Mon Sep 17 00:00:00 2001 From: Jonathan Rainville Date: Thu, 11 Jul 2019 16:15:04 -0400 Subject: [PATCH] feat(@embark/site): add documentation on minimalContractSize --- site/source/docs/contracts_configuration.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/site/source/docs/contracts_configuration.md b/site/source/docs/contracts_configuration.md index 8303bba12..c7c064cd3 100644 --- a/site/source/docs/contracts_configuration.md +++ b/site/source/docs/contracts_configuration.md @@ -347,6 +347,17 @@ tracking: 'path/to/some/file' Having the file referenced above under version control ensures that other users of our project don't redeploy the Smart Contracts on different platforms. + +### Reducing contract size + +To reduce the size of the contract JSON files that are included in the build directory, you can set `minimalContractSize` to `true`. It defaults to `false`. +When set to `true`, Embark will not put te bytecode, gas estimates and other big configurations in the JSON file. + +``` +minimalContractSize: true +``` + + ## Deployment hooks Sometimes we want to execute certain logic when Smart Contracts are being deployed or after all of them have been deployed. In other cases, we'd even like to control whether a Smart Contract should be deployed in the first place. For those scenarios, Embark lets us define the deployment hooks `beforeDeploy`, `deployIf`, `onDeploy` and `afterDeploy`.