embark/packages/plugins/basic-pipeline/README.md

# `embark-basic-pipeline`

> Basic pipeline for Embark that builds a DApp's frontend assets using webpack

Visit [framework.embarklabs.io](https://framework.embarklabs.io/) to get started with
[Embark](https://github.com/embarklabs/embark).

Contracts in `test/fixture/contracts` are from [OpenZeppelin](https://github.com/OpenZeppelin/openzeppelin-solidity) and [Gnosis Prediction Markets](https://github.com/gnosis/pm-contracts)
refactor(@embark/embarkjs): move module into own package (#1945) TODO: The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could assume that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions? 2019-10-14 16:05:17 +09:00			# `embark-basic-pipeline`

			`> Basic pipeline for Embark that builds a DApp's frontend assets using webpack`

chore: update site urls 2020-01-19 15:19:30 -05:00			`Visit [framework.embarklabs.io](https://framework.embarklabs.io/) to get started with`
chore: rename org references from embark-framework to embarklabs 2020-01-16 14:37:59 -05:00			`[Embark](https://github.com/embarklabs/embark).`
refactor(@embark/embarkjs): move module into own package (#1945) TODO: The `embark eject-webpack` command needs to be updated. @michaelsbradleyjr - do you have suggestions as to how we could port this over? We could assume that the `basic-pipeline` plugin will be installed, and then read the embark config and overrides from the file system, however this feels like we are sort adding a dependency to a plugin, which is not right. Any suggestions? 2019-10-14 16:05:17 +09:00
			Contracts in `test/fixture/contracts` are from [OpenZeppelin](https://github.com/OpenZeppelin/openzeppelin-solidity) and [Gnosis Prediction Markets](https://github.com/gnosis/pm-contracts)