embark/packages/embark-pipeline/src
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
..
babel-loader-overrides.js refactor(@embark/pipeline): move pipeline into own package 2019-05-15 19:59:59 +02:00
index.js feat(@embark/pipeline): enable choosing which fields to filter out 2019-08-01 13:53:47 -04:00
webpack.config.js refactor: upgrade to web3 v1.2.1 2019-08-07 11:01:23 -05:00
webpackConfigReader.js refactor: move `dappPath`, `ipcPath` and `embarkPath` into @embark/utils 2019-05-17 11:25:40 +02:00
webpackProcess.js fix(@embark/pipeline): check if config arg of writeStats is falsy 2019-08-09 10:37:20 -05:00