embark/packages/embark-core
Michael Bradley, Jr fd09488e4b fix(@embark/core): move process.on inside ProcessWrapper's constructor
This avoids mistakenly placing process event handlers on the parent process
whenever the `embark-core` package is loaded. Also, don't listen for an
`'exit'` event on `process` and then call `process.exit(0)` since the event "is
emitted after the child process ends" ([docs][docs]), i.e. it's unnecessary to
do so and in any case it's not correct to always exit with code `0`.

[docs]: https://nodejs.org/docs/latest-v10.x/api/child_process.html#child_process_event_exit
2019-05-08 15:55:06 -05:00
..
src fix(@embark/core): move process.on inside ProcessWrapper's constructor 2019-05-08 15:55:06 -05:00
.npmrc refactor(@embark/core): create embark-core package, move constants into embark-core 2019-04-30 12:11:25 -05:00
README.md refactor(@embark/core): create embark-core package, move constants into embark-core 2019-04-30 12:11:25 -05:00
constants.json feat(@embark/storage): Add command `service ipfs on/off` 2019-05-03 14:52:55 -04:00
package.json refactor(@embark/i18n): expose __ from embark-i18n, drop global __ 2019-05-08 11:01:16 +02:00
tsconfig.json refactor(@embark/core): create embark-core package, move constants into embark-core 2019-04-30 12:11:25 -05:00
tslint.json refactor(@embark/core): create embark-core package, move constants into embark-core 2019-04-30 12:11:25 -05:00

README.md

embark-core

Core library for Embark

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