embark/packages/embark-vyper
Michael Bradley, Jr df0064f1a9 build: use package.json "files" instead of .npmignore
`package.json` allows for a [`"files"` whitelist][files] to be specified as an
alternative to a top-level `.npmignore` within a package root. Maintaining
whitelists is generally easier and less error-prone than maintaining
blacklists, so implement a `"files"` list for all non-private packages in the
monorepo and remove unneeded `.npmignore` files.

Switch `embark-reset` from being a private package to one that will be
published, adjust the workspace's `"nohoist"` setting accordingly, and no
longer specify `embark-reset` as a bundled dependency of `packages/embark`. I
originally thought there might be a good reason not to publish it, but I no
longer think so.

Remove unnecessary LICENSE files in `packages/{embark,embark-ui}` since Lerna
will automatically copy the root LICENSE into any packages lacking that file,
i.e. before tarballs are packed and published to the NPM registry.

Change the `"author"` field of `packages/embarkjs-connector-web3` to match the
other packages, i.e. such that it matches the copyright assignment in the root
LICENSE. If that's not a desirable thing to do, then instead that package can
have a separate LICENSE file that has a copyright assignment for `"Jonathan
Rainville"`.

Supply some missing `.npmrc` files in `packages/*`.

[files]: https://docs.npmjs.com/files/package.json#files
2019-03-12 07:50:25 -04:00
..
src fix(vyper): file path 2019-02-20 14:15:41 +01:00
.npmrc build: use package.json "files" instead of .npmignore 2019-03-12 07:50:25 -04:00
README.md refactor(@embark/embark-vyper) move vyper to its own module 2019-02-06 14:32:54 -05:00
package.json build: use package.json "files" instead of .npmignore 2019-03-12 07:50:25 -04:00
tsconfig.json fix: supply missing tsconfig.json in packages/* 2019-02-06 17:20:13 -06:00
tslint.json refactor(@embark/embark-vyper) move vyper to its own module 2019-02-06 14:32:54 -05:00

README.md

Embark Compiler module

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 -