embark/packages
Pascal Precht a7edca0be8 fix(@embark/core): don't exit in Engine consumer API
`Engine.startEngine(cb)` potentially exits the current process if
any registered plugins emits an error in the bootstrap phase.

This limits consumers of this API to react accordingly. Embark's APIs
should be considered library APIs that propagate errors, but let callers
decide what to do with them.

This commit ensures we keep propagating the error of `startEngine()` without
exiting the current process.
2019-11-29 12:57:19 +01:00
..
cockpit build(deps): bump core-js from 3.3.5 to 3.4.3 2019-11-26 15:16:29 -06:00
core fix(@embark/core): don't exit in Engine consumer API 2019-11-29 12:57:19 +01:00
embark fix(@embark/core): don't exit in Engine consumer API 2019-11-29 12:57:19 +01:00
embarkjs build(deps): bump core-js from 3.3.5 to 3.4.3 2019-11-26 15:16:29 -06:00
plugins chore(@embark/whisper): Remove CHANGELOG’s for new modules 2019-11-29 11:44:32 +01:00
stack build(deps): bump core-js from 3.3.5 to 3.4.3 2019-11-26 15:16:29 -06:00
utils build(deps): bump core-js from 3.3.5 to 3.4.3 2019-11-26 15:16:29 -06:00
.yarnrc build: cleanup .yarnrc 2019-02-05 14:15:39 -06:00