Go to file
Dan Finlay de1bd04bfc Add travis compiler addons 2016-04-14 14:46:08 -07:00
app Moved UI into repo with its own dependency stack 2016-04-13 15:28:44 -07:00
test Migrate etherscan providers to our RPC 2016-04-12 14:16:39 -07:00
ui Move UI deps into main plugin package.json 2016-04-13 15:46:39 -07:00
.babelrc Added basic es6 mocha test suite 2016-03-24 17:51:46 -07:00
.editorconfig init commit 2015-07-31 18:38:02 -07:00
.gitattributes init commit 2015-07-31 18:38:02 -07:00
.gitignore Created etherscan provider (untested) 2016-03-29 14:31:25 -07:00
.jshintrc init commit 2015-07-31 18:38:02 -07:00
.travis.yml Add travis compiler addons 2016-04-14 14:46:08 -07:00
.yo-rc.json init commit 2015-07-31 18:38:02 -07:00
CHANGELOG.md Add merge to changelog 2016-04-13 15:47:40 -07:00
README.md Remove private throughput graph 2016-04-13 16:21:17 -07:00
gulpfile.js Moved UI into repo with its own dependency stack 2016-04-13 15:28:44 -07:00
package.json Bump ethereumjs-utils version 2016-04-14 14:34:52 -07:00
svg-notifications.md notifications - add tx confirm+cancel buttons 2016-03-11 17:13:48 -08:00

README.md

Metamask Plugin

Development

npm install

Developing with Gulp

We're using an experimental version of gulp-cli, so if you have the old version of gulp, you'll need to uninstall it, npm uninstall -g gulp, and install this one instead:

npm install gulpjs/gulp-cli#4.0 -g

After that, you can just:

gulp dev

In Chrome

Open Settings > Extensions.

Check "Developer mode".

At the top, click Load Unpacked Extension.

Navigate to your metamask-plugin/dist folder.

Click Select.

You now have the plugin, and can click 'inspect views: background plugin' to view its dev console.

Developing the UI

To enjoy the live-reloading that gulp dev offers while working on the web3-provider-engine or other dependencies:

  1. Clone the dependency locally.
  2. npm install in its folder.
  3. Run npm link in its folder.
  4. Run npm link $DEP_NAME in this project folder.
  5. Next time you gulp dev it will watch the dependency for changes as well!

Running Tests

Currently the tests are split between two suites (we recently merged the UI into the main plugin repository). There are two different test suites to be concerned with:

Plugin tests, npm test. UI tests, npm run testUi.

You can also run both of these with continuously watching processes, via npm run watch and npm run watchUi.

UI Testing Particulars

Requires mocha installed. Run npm install -g mocha.

You can either run the test suite once with npm testUi, or you can reload on file changes, by running mocha watch ui/test/**/**.

Deploying the UI

You must be authorized already on the Metamask plugin.

  1. Update the version in app/manifest.json and the Changelog in CHANGELOG.md.
  2. Visit the chrome developer dashboard.
  3. Zip the dist folder in this repository.
  4. Upload that zip file as the updated package.