A Metamask fork with Infura removed and default networks editable
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Dan Finlay e0ee4365cb Merge pull request #104 from MetaMask/TargetEtherscanAtOurRpc 9 years ago
app Point rawtestrpc at new testrpc 9 years ago
test Migrate etherscan providers to our RPC 9 years ago
.babelrc Added basic es6 mocha test suite 9 years ago
.editorconfig init commit 9 years ago
.gitattributes init commit 9 years ago
.gitignore Created etherscan provider (untested) 9 years ago
.jshintrc init commit 9 years ago
.yo-rc.json init commit 9 years ago
CHANGELOG.md Bump changelog 9 years ago
README.md Added changelog and deploy docs 9 years ago
gulpfile.js build - use gulp, remove grunt 9 years ago
package.json Revert "Revert "Etherscan provider"" 9 years ago
svg-notifications.md notifications - add tx confirm+cancel buttons 9 years ago

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 metamask-ui or web3-provider-engine 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!

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.