embark/packages
emizzle eca456f4cb fix(@embark/storage): Fix hang when IPFS/Swarm started externally
Fix hang when the storage provider (IPFS or Swarm) was started externally before running Embark.

If IPFS/Swarm was already running before `embark run` was run, then the relevant `registerProvider` and `setProvider` code was not being run through the console, and thus the module init event was never fired, preventing the DApp from being built.

This PR refactors the way the IPFS/Swarm process is launched so that the `registerProvider` and `setProvider` code snippets are run through the console in the case of:
* IPFS/Swarm running externally from Embark
* IPFS/Swarm started in a child process by Embark
* Storage is disabled in the DApp config
2019-03-26 17:35:27 -04:00
..
embark fix(@embark/storage): Fix hang when IPFS/Swarm started externally 2019-03-26 17:35:27 -04:00
embark-async-wrapper chore(release): 4.0.0 2019-03-18 18:26:56 -05:00
embark-compiler chore(release): 4.0.0 2019-03-18 18:26:56 -05:00
embark-graph chore(release): 4.0.0 2019-03-18 18:26:56 -05:00
embark-reset chore(release): 4.0.0 2019-03-18 18:26:56 -05:00
embark-typings chore(release): 4.0.0 2019-03-18 18:26:56 -05:00
embark-ui refactor(@cockpit): unregister the service worker 2019-03-26 16:00:13 -04:00
embark-vyper chore(release): 4.0.0 2019-03-18 18:26:56 -05:00
embarkjs fix(@embark/storage): Fix hang when IPFS/Swarm started externally 2019-03-26 17:35:27 -04:00
embarkjs-connector-web3 chore(release): 4.0.0 2019-03-18 18:26:56 -05:00
.yarnrc build: cleanup .yarnrc 2019-02-05 14:15:39 -06:00