36faee932f | ||
---|---|---|
.github | ||
common | ||
electron-app | ||
jenkins | ||
jest_config | ||
scripts | ||
shared/types | ||
spec | ||
static | ||
webpack_config | ||
.drawbridgerc | ||
.editorconfig | ||
.gitignore | ||
.npmrc | ||
.nvmrc | ||
.prettierignore | ||
.prettierrc | ||
.travis.yml | ||
LICENSE | ||
README.md | ||
package.json | ||
tsconfig.json | ||
tslint.json | ||
yarn.lock |
README.md
MyCrypto Web & Desktop Apps
- Just looking to download? Grab our latest release.
- Looking for the old site? Check out https://legacy.mycrypto.com or the source at MyCryptoHQ/mycrypto.com
Requirements
- Node 8.9.4*
- Yarn >= 1.7.0**
- Python 2.7.X***
*Higher versions should work fun, but may cause inconsistencies. It's suggested you run 8.9.4 using nvm
.
**npm is NOT supported for package management. MyCrypto uses yarn.lock to ensure sub-dependency versions are pinned, so yarn is required to install node_modules
***Python 3 is not supported, since our dependencies use node-gyp
.
Running the App
After yarn
ing all dependencies you can run various commands depending on what you want to do:
Development
# run app in dev mode in browser, rebuild on file changes
yarn dev
# run app in dev mode in electron, rebuild on file changes
yarn dev:electron
Build Releases
# builds the production server app
yarn build
# builds the downloadable version of the site
yarn build:downloadable
# builds the electron apps
yarn build:electron
# builds only one OS's electron app
yarn build:electron:(osx|linux|windows)
All of these builds are output to a folder in dist/
.
Unit Tests:
# run unit tests with Jest
yarn test
Integration Tests:
# run integration tests with Jest
yarn test:int
Dev (HTTPS):
Some parts of the site, such as the Ledger wallet, require an HTTPS environment to work. To develop on HTTPS, do the following:
- Create your own SSL Certificate (Heroku has a nice guide here)
- Move the
.key
and.crt
files intowebpack_config/server.*
- Run the following command:
yarn dev:https
Address Derivation Checker:
EthereumJS-Util previously contained a bug that would incorrectly derive addresses from private keys with a 1/128 probability of occurring. A summary of this issue can be found here.
As a reactionary measure, the address derivation checker was created.
To test for correct address derivation, the address derivation checker uses multiple sources of address derivation (EthereumJS and PyEthereum) to ensure that multiple official implementations derive the same address for any given private key.
The derivation checker utility assumes that you have:
- Docker installed/available
- dternyak/eth-priv-to-addr pulled from DockerHub
Docker setup instructions:
- Install docker (on macOS, Docker for Mac is suggested)
docker pull dternyak/eth-priv-to-addr
Run Derivation Checker
The derivation checker utility runs as part of the integration test suite.
yarn test:int
Folder structure:
│
├── common
│ ├── actions - Application actions
│ ├── api - Services and XHR utils
│ ├── assets - Images, fonts, etc.
│ ├── components - Components according to "Redux philosophy"
│ ├── config - Various config data and hard-coded json
│ ├── containers - Containers according to "Redux philosophy"
│ ├── libs - Framework-agnostic libraries and business logic
│ ├── reducers - Redux reducers
│ ├── sagas - Redux sagas
│ ├── sass - SCSS styles, variables, mixins
│ ├── selectors - Redux selectors
│ ├── translations - Language JSON dictionaries
│ ├── typescript - Typescript definition files
│ ├── utils - Common use utility functions
│ ├── index.tsx - Entry point for app
│ ├── index.html - Html template file for html-webpack-plugin
│ ├── Root.tsx - Root component for React
│ └── store.ts - Redux reducer combiner and middleware injector
├── electron-app - Code for the native electron app
├── jest_config - Jest testing configuration
├── spec - Jest unit tests, mirror's common's structure
├── static - Files that don't get compiled, just moved to build
└── webpack_config - Webpack configuration
More information is available on the Wiki Pages
Thanks & Support
Cross browser testing and debugging provided by the very lovely team at BrowserStack.