embark/dapps/tests/contracts/embark.json

{
  "contracts": [
    "contracts/**"
  ],
  "app": {},
  "buildDir": "build/",
  "config": {
    "contracts": "contracts.js",
    "storage": false,
    "communication": false,
    "webserver": false,
    "namesystem": "ens.json"
  },
  "versions": {
    "solc": "0.4.26"
  },
  "plugins": {
    "embark-geth": {},
    "embark-parity": {},
    "embark-profiler": {},
    "embark-graph": {}
  }
}
add test_app for test purposes 2017-02-09 19:38:02 -05:00			`{`
fix(test/blockchain): fix race condition of installing web3 and test 2019-02-12 09:02:17 -05:00			`"contracts": [`
			`"contracts/**"`
			`],`
update contracts appp 2018-03-29 18:35:10 -04:00			`"app": {},`
			`"buildDir": "build/",`
revert versions update for now; support granular config on embark json 2018-03-31 21:06:00 -04:00			`"config": {`
fix(@embark/cmd-controller): exit build if afterDeploy is not array Before, `embark build` would wait at the end if there was an afterDeploy, because there was no way with the old string and array syntax to know when the commands were done. Now, with the function syntax, we can wait for the end. This way, we can exit the build at the end if it is a function afterDeploy. Otherwise, we show a message saying that they should update 2020-01-31 11:29:38 -05:00			`"contracts": "contracts.js",`
revert versions update for now; support granular config on embark json 2018-03-31 21:06:00 -04:00			`"storage": false,`
			`"communication": false,`
ens resolve 2018-10-05 14:49:10 +05:30			`"webserver": false,`
			`"namesystem": "ens.json"`
revert versions update for now; support granular config on embark json 2018-03-31 21:06:00 -04:00			`},`
support versions on embark json config 2018-03-31 19:35:20 -04:00			`"versions": {`
feat: support Node.js v12.x and newer Remove the `<12.0.0` restriction re: Node.js version in the `"engines"` settings for all the packages in the monorepo that had that restriction. Add missing `"engines"` settings in `packages/plugins/snark/package.json`. Adjust the Azure Pipelines config to include builds for Node.js v12.x and v13.x. Bump `solc` to `0.4.26` in `dapps/tests/app` and `dapps/tests/contracts`. It was discovered that older versions suffered a fatal `Maximum call stack size exceeded` error when run on Windows with Node.js v12.x or newer. Display a warning re: the bad combo (solc version + Windows + Node version) if it's detected at runtime. Adjust the root `yarn.lock` so that the `sha3` transitive dependency resolves to a newer version that is compatible with Node v13.x. 2020-01-17 11:32:32 -06:00			`"solc": "0.4.26"`
fix(test/blockchain): fix race condition of installing web3 and test 2019-02-12 09:02:17 -05:00			`},`
			`"plugins": {`
feat: warn about packages not configured as plugins; make geth/parity full plugins feat(@embark/utils): add method to verify if a plugin is installed & configured feature(@embark/utils): add method to verify if a plugin is installed & configured feature: warn about packages that will be independent plugins and are not configured chore: update templates to specify plugins refactor: add to plugin api params so that blockchain plugins no longer need to be passed options address changes in code review remove unneded space Update packages/core/utils/src/index.ts Co-Authored-By: Jonathan Rainville <rainville.jonathan@gmail.com> Update packages/core/utils/src/index.ts Co-Authored-By: Michael Bradley <michaelsbradleyjr@gmail.com> fix linting issue add missing import update dependency fix plugins object add missing whitespace 2020-01-22 12:36:39 -05:00			`"embark-geth": {},`
			`"embark-parity": {},`
			`"embark-profiler": {},`
			`"embark-graph": {}`
support versions on embark json config 2018-03-31 19:35:20 -04:00			`}`
add test_app for test purposes 2017-02-09 19:38:02 -05:00			`}`