embark/packages/embark-compiler
Michael Bradley, Jr d5c984c592 build: use babel cli's --extensions consistently in all packages
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.
2019-05-02 20:33:42 -05:00
..
2019-02-12 08:24:20 +00:00
2019-03-18 18:26:56 -05:00

embark-compiler

Embark compiler module

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

This module abstracts the compiler interface. It exposes a plugin api to register contract extensions and how to handle them. It accepts command requests to compile and returns the aggregated compilation result.

API

command: compiler:contracts

arguments:

  • contractFiles -
  • options -