embark/packages/embark-pipeline
Michael Bradley, Jr 9d81fc5b1c fix(@embark/pipeline): check if config arg of writeStats is falsy
When passing the name of a build pipeline that doesn't exist, e.g.
`embark run|build --pipeline foo`, `writeStats` would cause an unhandled
promise rejection because its config argument is falsy. Checking for that and
returning early from `writeStats` allows the `"no webpack config has the name
'foo'"` error to be reported correctly.
2019-08-09 10:37:20 -05:00
..
src fix(@embark/pipeline): check if config arg of writeStats is falsy 2019-08-09 10:37:20 -05:00
.babelrc.js fix(@embark/pipeline): adjust ignore paths 2019-08-09 10:37:20 -05:00
.npmrc refactor(@embark/pipeline): move pipeline into own package 2019-05-15 19:59:59 +02:00
CHANGELOG.md chore(release): 4.1.0-beta.5 2019-07-10 16:21:47 -05:00
README.md refactor(@embark/pipeline): move pipeline into own package 2019-05-15 19:59:59 +02:00
package.json chore(release): 4.1.0-beta.5 2019-07-10 16:21:47 -05:00
tsconfig.json refactor(@embark/pipeline): move pipeline into own package 2019-05-15 19:59:59 +02:00
tslint.json refactor(@embark/pipeline): move pipeline into own package 2019-05-15 19:59:59 +02:00

README.md

embark-pipeline

Build pipeline module for Embark

Visit embark.status.im to get started with Embark.