remove code not beloging to code runner & other core modules; disable code generator and move contract code to its own module
cleanup pipeline; start preparing for plugin based pipeline file generation
initial work to write pipeline files through an api
add action events to pipeline; generate contracts json and js files
move old pipeline to its own module; generate basic artifacts
re-add missing plugins function
add basic embarkjs provider registration
refactor embark-whisper; move whisper api; execute whisper code in console
add api to register help cmds in console; start moving hardcoded help cmds out
cleanup embark-graph
add todos
If a package uses only `.js` then supply `--extensions ".js"`. If a package
uses only `.ts` then supply `--extensions ".ts"`. If a package uses both, then
supply `--extensions ".js,.ts"`.
The reason for this is that adding/removing TS/JS support ought to occasion
revising a package's `package.json` file and adjusting other scripts as well,
e.g. for linting. With these changes, it won't work to simply start adding
`.ts` files in a package's `src/` directory, which should prompt the developer
to review `package.json` and make the appropriate changes, and/or other
developers may realize changes need to be made during code review.
This commit has been originally cherry-picked from d0d89fc5ae and
slightly modified to update all packages, as meanwhile, new packages have been added to `master`.
The reason this commit is cherry-picked from `4.0.x` branch is because
it wasn't created from `master`.
Purpose is mainly to update `CHANGELOG` and get the package versions in sync again.
feature(@embark/embarkjs-whisper: make embarkjs whisper plugin a module on its own
feature(@embark/embarkjs-whisper: make embarkjs whisper plugin a module on its own
Iuri Matias
Michael Bradley, Jr
Andre Medeiros