Pascal Precht de8f2170ba fix(plugins/solc): don't read pluginConfig from plugin.config
In https://github.com/embarklabs/embark/pull/2330#discussion_r389906144 we've changed the `solc` plugin to read its
`pluginConfig` from `embark.config`. This was done under the assumption that
the `embark.config` is always properly populated with a dedicated `pluginConfig`.
In our testing environment we pass `Embark` objects to plugins, while in reality, we pass `Plugin` instances.
These two are different in nature, so relying on `embark.config` inside the plugin seemed the
most pragmatic way forward without introducing a bigger refactoring in the testing APIs.

Unfortunately it turned out that `embark.config` isn't populated with a `pluginConfig`
which essentially caused it to break apps.

This commit reverts that change done in the mentioned PR and patches the Embark testing
API to behave like a `Plugin` while still being an `Embark` instance.
2020-04-02 10:55:58 +02:00
..
2020-01-28 12:07:17 -05:00

embark-solc

Solc plugin for Embark

Compiles contracts using solc in an Embark DApp.

Installation

In your embark dapp directory:

npm install embark-solc --save

Then add embark-solc to the plugins section in embark.json:

"plugins": {
  "embark-solc": {
    "outputBinary": false
  }
}
  • outputBinary can be specified to generate a .bin file that contains the binary of the contracts in hex. Default value is false.

Requirements

  • Embark 4.0.0 or higher
  • Solc installed and available globally on your machine (h)

Visit framework.embarklabs.io to get started with Embark.