Skip to content
Yoroi Wallet - Chrome extension (React frontend)
Branch: develop
Clone or download
Latest commit 47cc99e Apr 22, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci speed up ci install Apr 18, 2019
app shin self review fix 1 Apr 22, 2019
chrome Update main_window.html (remove 500px width) Apr 16, 2019
config Fixed testnet banner to display actual network name. Fixed staging ne… Apr 13, 2019
docs first step Apr 18, 2019
features fix e2e test Apr 19, 2019
flow fix bad type causing problems with HW wallets Apr 10, 2019
scripts Remove DllPlugin from webpack Apr 16, 2019
webpack Remove DllPlugin from webpack Apr 16, 2019
.eslintrc Cardano redeem (#279) Feb 17, 2019
.flowconfig fix trezor-connect flow error Jan 11, 2019
.gitignore Demove dll folders from .ignore files Apr 16, 2019
.nvmrc forgot nvmrc Apr 18, 2019
LICENSE first working version Apr 9, 2019
appveyor.yml Initial commit Mar 12, 2018
babel.config.js fix config conflict Apr 18, 2019
jest.config.js fix config conflict Apr 18, 2019
package-lock.json fix tests broken by wasm migration Apr 17, 2019
package.json bump npm Apr 18, 2019

Yoroi - Cardano ADA wallet


Check out our documents on the governance of this project.

First-time setup (or branch change)

Build Yoroi Chrome extension

Extension can be built for both the Cardano mainnet and testnet:

  • Localhost (recommended)
# build files to './dev'
$ npm run dev
  • Mainnet
# build files to './build'
$ npm run build -- --env "mainnet"
  • Testnet (not supported yet)
# build files to './build'
$ npm run build -- --env "testnet"

Run Yoroi Chrome extension

  1. Open new webpage with chrome://extensions
  2. Turn on the developer mode (checkbox in the top right-hand corner)
  3. Press Load unpacked
  4. Select either dev or build folder (depending which npm command you ran)

Note: dev should hot reload on code change

Run Yoroi Firefox extension

Debug builds are not maintained for Firefox as firefox rejects manifest files with non-https localhost in them. You can bypass this by manually adding the extension into your Firefox folder but this is kind of tedious. I suggest instead installing the mainnet build as it does not use localhost. (through about:debugging or about:addons). See for how to makes the unittests pass.

Build release candidate


Selenium + Cucumber

You must run npm run test-prepare before running the tests!

test-prepare will BUILD the extension and then the tests will LOAD the extension.

Rerun test-prepare anytime you make changes to the application itself. If you only change test files, you do not need to rerun it.

# flow
$ npm run flow
# lint
$ npm run eslint
# features (command to run all existing tests)
$ npm run test-e2e-chrome
# How to run one .feature file (One feature file = one covered component from youtrack)
$ npm run test-by-feature feature/wallet-creation.feature
# How to run one test.
$ npm run test-by-tag @it-10


We use Jest for unittests.

$ npm run jest



You can’t perform that action at this time.