m/metamask-extension
1
0
Fork 0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-11-22 01:47:00 +01:00
Code
🦊 Minimalized version of MetaMask for my own personal use.
12,006 Commits 2 Branches 0 Tags 265 MiB
JavaScript 83.4%
TypeScript 12.8%
SCSS 3.5%
Shell 0.2%
HTML 0.1%
fbbdaf04ed
Go to file
Daniel fbbdaf04ed
Increase Jest unit test coverage for the Swaps feature to ~25% (#10900) 
* Swaps: Show a network name dynamically in a tooltip

* Replace “Ethereum” with “$1”, change “Test” to “Testnet”

* Replace 이더리움 with $1

* Translate network names, use ‘Ethereum’ by default if a translation is not available yet

* Reorder messages to resolve ESLint issues

* Add a snapshot test for the FeeCard component, increase Jest threshold

* Enable snapshot testing into external .snap files in ESLint

* Add the “networkNameEthereum” key in ko/messages.json, remove default “Ethereum” value

* Throw an error if chain ID is not supported by the Swaps feature

* Use string literals when calling the `t` fn,

* Watch Jest tests silently (no React warnings in terminal, only errors)

* Add @testing-library/jest-dom, import it before running Jest tests

* Add snapshot testing of Swaps’ React components for happy paths, increase minimum threshold for Jest

* Add the test/jest folder for Jest setup and shared functions, use it in Swaps Jest tests

* Fix ESLint issues, update linting config

* Enable ESLint for .snap files (Jest snapshots), throw an error if a snapshot is bigger than 50 lines

* Don’t run lint:fix for .snap files

* Move `createProps` outside of `describe` blocks, move store creation inside tests

* Use translations instead of keys, update a rendering function to load translations

* Make sure all Jest snapshots are shorter than 50 lines (default limit)

* Add / update props for Swaps tests

* Fix React warnings when running tests for Swaps
2021-04-21 12:34:35 -07:00
.circleci Jest config (#10855) 2021-04-09 10:20:32 -07:00
.github @metamask/contract-metadata (#9968) 2020-12-01 14:55:01 -08:00
.storybook fix: remove unused metamask.rpcUrl from redux state + fix tests to reflect that (#10714) 2021-03-24 15:54:24 -07:00
app Adding option to set Custom Nonce to Confirm Approve Page (#10595) 2021-04-16 18:00:18 -04:00
development Fix crash when adding new changelog release header (#10870) 2021-04-09 20:50:06 -02:30
docs remove matomo and route to segment (#9646) 2020-10-26 14:05:57 -05:00
lavamoat/node remove node-sass dependency (#10797) 2021-04-02 11:57:05 -02:30
patches Dep upgrades and patches (#10903) 2021-04-20 13:39:49 +08:00
shared Handling infura blockage (#10883) 2021-04-15 10:41:40 -07:00
test Increase Jest unit test coverage for the Swaps feature to ~25% (#10900) 2021-04-21 12:34:35 -07:00
ui Increase Jest unit test coverage for the Swaps feature to ~25% (#10900) 2021-04-21 12:34:35 -07:00
.editorconfig Clean EditorConfig file 2019-05-23 07:17:42 -02:30
.eslintrc.js Increase Jest unit test coverage for the Swaps feature to ~25% (#10900) 2021-04-21 12:34:35 -07:00
.gitattributes Use Infura v3 API (#9368) 2020-09-10 13:46:00 -02:30
.gitignore Jest config (#10855) 2021-04-09 10:20:32 -07:00
.metamaskrc.dist add segment implementation of metametrics (#9382) 2020-09-14 12:04:05 -05:00
.nvmrc Update to Node v14 (#9514) 2021-02-03 13:45:38 +08:00
.prettierignore Add jest-coverage/ to prettierignore (#10865) 2021-04-09 11:16:19 -07:00
.prettierrc.yml @metamask/eslint config@5.0.0 (#10358) 2021-02-04 10:15:23 -08:00
.yarnrc Add .yarnrc to disable scripts (#10354) 2021-02-03 21:53:12 -03:30
babel.config.js @metamask/eslint config@5.0.0 (#10358) 2021-02-04 10:15:23 -08:00
CHANGELOG.md Add categories to each changelog release (#10837) 2021-04-07 13:12:07 -02:30
jest.config.js Increase Jest unit test coverage for the Swaps feature to ~25% (#10900) 2021-04-21 12:34:35 -07:00
jsconfig.json no more node:console (#10640) 2021-03-12 14:41:58 -06:00
LICENSE Add new license (#9282) 2020-08-20 16:01:22 -07:00
nyc.config.js @metamask/eslint config@5.0.0 (#10358) 2021-02-04 10:15:23 -08:00
package.json Increase Jest unit test coverage for the Swaps feature to ~25% (#10900) 2021-04-21 12:34:35 -07:00
README.md Improve contributor documentation in README (#10509) 2021-02-24 12:22:42 -03:30
stylelint.config.js @metamask/eslint-config*@6.0.0 (#10858) 2021-04-08 14:34:55 -07:00
yarn.lock Increase Jest unit test coverage for the Swaps feature to ~25% (#10900) 2021-04-21 12:34:35 -07:00

README.md

MetaMask Browser Extension

Hey! We are hiring JavaScript Engineers! Apply here!

You can find the latest version of MetaMask on our official website. For help using MetaMask, visit our User Support Site.

For general questions, feature requests, or developer questions, visit our Community Forum.

MetaMask supports Firefox, Google Chrome, and Chromium-based browsers. We recommend using the latest available browser version.

For up to the minute news, follow our Twitter or Medium pages.

To learn how to develop MetaMask-compatible applications, visit our Developer Docs.

To learn how to contribute to the MetaMask project itself, visit our Internal Docs.

Building locally

  • Install Node.js version 14
    • If you are using nvm (recommended) running nvm use will automatically choose the right node version for you.
  • Install Yarn
  • Install dependencies: yarn setup (not the usual install command)
  • Copy the .metamaskrc.dist file to .metamaskrc
    • Replace the INFURA_PROJECT_ID value with your own personal Infura Project ID.
    • If debugging MetaMetrics, you'll need to add a value for SEGMENT_WRITE_KEY Segment write key.
  • Build the project to the ./dist/ folder with yarn dist.

Uncompressed builds can be found in /dist, compressed builds can be found in /builds once they're built.

Contributing

Development builds

To start a development build (e.g. with logging and file watching) run yarn start.

To start the React DevTools and Redux DevTools Extension alongside the app, use yarn start:dev.

  • React DevTools will open in a separate window; no browser extension is required
  • Redux DevTools will need to be installed as a browser extension. Open the Redux Remote Devtools to access Redux state logs. This can be done by either right clicking within the web browser to bring up the context menu, expanding the Redux DevTools panel and clicking Open Remote DevTools OR clicking the Redux DevTools extension icon and clicking Open Remote DevTools.
    • You will also need to check the "Use custom (local) server" checkbox in the Remote DevTools Settings, using the default server configuration (host localhost, port 8000, secure connection checkbox unchecked)

Running Unit Tests and Linting

Run unit tests and the linter with yarn test.

To run just unit tests, run yarn test:unit. To run unit tests continuously with a file watcher, run yarn watch.

You can run the linter by itself with yarn lint, and you can automatically fix some lint problems with yarn lint:fix. You can also run these two commands just on your local changes to save time with yarn lint:changed and yarn lint:changed:fix respectively.

Running E2E Tests

Our e2e test suite can be run on either Firefox or Chrome. In either case, start by creating a test build by running yarn build:test.

Firefox e2e tests can be run with yarn test:e2e:firefox.

Chrome e2e tests can be run with yarn test:e2e:chrome, but they will only work if you have Chrome v79 installed. Update the chromedriver package to a version matching your local Chrome installation to run e2e tests on newer Chrome versions.

Changing dependencies

Whenever you change dependencies (adding, removing, or updating, either in package.json or yarn.lock), there are various files that must be kept up-to-date.

  • yarn.lock:
    • Run yarn setup again after your changes to ensure yarn.lock has been properly updated.
  • The allow-scripts configuration in package.json
    • Run yarn allow-scripts auto to update the allow-scripts configuration automatically. This config determines whether the package's install/postinstall scripts are allowed to run. Review each new package to determine whether the install script needs to run or not, testing if necessary.
    • Unfortunately, yarn allow-scripts auto will behave inconsistently on different platforms. macOS and Windows users may see extraneous changes relating to optional dependencies.
  • The LavaMoat auto-generated policy in lavamoat/node/policy.json
    • Run yarn lavamoat:auto to re-generate this policy file. Review the changes to determine whether the access granted to each package seems appropriate.
    • Unfortunately, yarn lavamoat:auto will behave inconsistently on different platforms. macOS and Windows users may see extraneous changes relating to optional dependencies.

Architecture

Architecture Diagram

Development

yarn
yarn start

Build for Publishing

yarn dist

Other Docs