m/metamask-extension
1
0
Fork 0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-11-25 20:02:58 +01:00
Code
🦊 Minimalized version of MetaMask for my own personal use.
11,097 Commits 2 Branches 0 Tags 265 MiB
JavaScript 83.4%
TypeScript 12.8%
SCSS 3.5%
Shell 0.2%
HTML 0.1%
cdfa2e66fd
Go to file
Mark Stacey cdfa2e66fd
Hide retry button for on-chain failures (#9506) 
On-chain failed transactions have a transaction status of `confirmed`,
and should not be retried. Our retry function doesn't handle on-chain
failures yet, so it would inevitably fail due to the transaction having
the same nonce as a confirmed on-chain transaction.

When determining whether to show the retry button in the UI, we had
mistakenly been using a `status` variable that determined whether we
should show "Failed" on that transaction in the activity log. That
display status includes both network and on-chain failures, unlike
the `txMeta.status` property.

The `showRetry` logic has been updated to ensure it's only shown when
`txMeta.status` is `failed`, meaning on-chain failures will no longer
show the retry button. Additionally, the display-specific `status`
variable has been renamed to `displayedStatusKey`, to indicate that it
is a string that corresponds to a localized message, and that it's the
status meant for display purposes.
2020-10-07 14:59:38 -07:00
.circleci Skip running e2e tests when commit is tagged with '[skip e2e]' (#9486) 2020-10-07 15:12:52 -02:30
.github
.storybook Add MetaMask Swaps (#9482) 2020-10-06 15:58:38 -02:30
app Fix version used by TransactionController#confirmTransaction (#9503) 2020-10-07 14:27:39 -07:00
development
docs
test Stop passing a gas param to the estimateGas call initiated in the swaps controller (#9501) 2020-10-07 16:30:17 -02:30
ui Hide retry button for on-chain failures (#9506) 2020-10-07 14:59:38 -07:00
.editorconfig
.eslintrc.js
.gitattributes
.gitignore
.metamaskrc.dist
.nvmrc
.prettierignore
babel.config.js
CHANGELOG.md
LICENSE
nyc.config.js
package.json Add MetaMask Swaps (#9482) 2020-10-06 15:58:38 -02:30
README.md
stylelint.config.js
yarn.lock Use node-forge@0.10.0 (#9473) 2020-10-01 16:37:07 -02:30

README.md

MetaMask Browser Extension

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

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 10
    • If you are using nvm (recommended) running nvm use will automatically choose the right node version for you.
  • Install Yarn
  • Install dependencies: yarn
  • 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.
  • Optionally, to start a development build (e.g. with logging and file watching) run yarn start instead.
    • 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)

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

Contributing

Running Tests

Run tests with yarn test.

You can also test with a continuously watching process, via yarn watch.

You can run the linter by itself with yarn lint.

Architecture

Architecture Diagram

Development

yarn
yarn start

Build for Publishing

yarn dist

Other Docs