1
0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-12-23 09:52:26 +01:00
metamask-extension/package.json

301 lines
11 KiB
JSON
Raw Normal View History

2015-08-01 03:38:02 +02:00
{
2015-10-10 08:14:18 +02:00
"name": "metamask-crx",
2015-08-01 03:38:02 +02:00
"version": "0.0.0",
"private": true,
2016-01-15 03:26:54 +01:00
"scripts": {
"start": "gulp dev:extension",
2018-09-25 23:30:53 +02:00
"dist": "gulp dist",
"doc": "jsdoc -c development/.jsdoc.json",
2018-09-12 23:10:06 +02:00
"publish-docs": "gh-pages -d docs/jsdocs",
"start:test": "gulp dev:test",
"build:test": "gulp build:test",
Switch from `npm` to `yarn` (#6843) As a solution to the constant lockfile churn issues we've had with `npm`, the project now uses `yarn` to manage dependencies. The `package-lock.json` file has been replaced with `yarn.lock`, which was created using `yarn import`. It should approximate the contents of `package-lock.json` fairly well, though there may be some changes due to deduplication. The codeowners file has been updated to reference this new lockfile. All documentation and npm scripts have been updated to reference `yarn` rather than `npm`. Note that running scripts using `npm run` still works fine, but it seemed better to switch those to `yarn` as well to avoid confusion. The `npm-audit` Bash script has been replaced with `yarn-audit`. The output of `yarn audit` is a bit different than `npm audit` in that it returns a bitmask to describe which severity issues were found. This made it simpler to check the results directly from the Bash script, so the associated `npm-audit-check.js` script was no longer required. The output should be exactly the same, and the information is still sourced from the same place (the npm registry). The new `yarn-audit` script does have an external dependency: `jq`. However, `jq` is already assumed to be present by another CI script, and is present on all CI images we use. `jq` was not added to `package.json` as a dependency because there is no official package on the npm registry, just wrapper scripts. We don't need it anywhere exept on CI anyway. The section in `CONTRIBUTING` about how to develop inside the `node_modules` folder was removed, as the advice was a bit dated, and wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
"test": "yarn test:unit && yarn lint",
2019-07-03 03:49:59 +02:00
"dapp": "static-server test/e2e/contract-test --port 8080",
Switch from `npm` to `yarn` (#6843) As a solution to the constant lockfile churn issues we've had with `npm`, the project now uses `yarn` to manage dependencies. The `package-lock.json` file has been replaced with `yarn.lock`, which was created using `yarn import`. It should approximate the contents of `package-lock.json` fairly well, though there may be some changes due to deduplication. The codeowners file has been updated to reference this new lockfile. All documentation and npm scripts have been updated to reference `yarn` rather than `npm`. Note that running scripts using `npm run` still works fine, but it seemed better to switch those to `yarn` as well to avoid confusion. The `npm-audit` Bash script has been replaced with `yarn-audit`. The output of `yarn audit` is a bit different than `npm audit` in that it returns a bitmask to describe which severity issues were found. This made it simpler to check the results directly from the Bash script, so the associated `npm-audit-check.js` script was no longer required. The output should be exactly the same, and the information is still sourced from the same place (the npm registry). The new `yarn-audit` script does have an external dependency: `jq`. However, `jq` is already assumed to be present by another CI script, and is present on all CI images we use. `jq` was not added to `package.json` as a dependency because there is no official package on the npm registry, just wrapper scripts. We don't need it anywhere exept on CI anyway. The section in `CONTRIBUTING` about how to develop inside the `node_modules` folder was removed, as the advice was a bit dated, and wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
"dapp-chain": "GANACHE_ARGS='-b 2' concurrently -k -n ganache,dapp -p '[{time}][{name}]' 'yarn ganache:start' 'sleep 5 && static-server test/e2e/contract-test --port 8080'",
"watch:test:unit": "nodemon --exec \"yarn test:unit\" ./test ./app ./ui",
"sendwithprivatedapp": "static-server test/e2e/send-eth-with-private-key-test --port 8080",
"test:unit": "cross-env METAMASK_ENV=test mocha --exit --require test/setup.js --recursive \"test/unit/**/*.js\" \"ui/app/**/*.test.js\"",
"test:unit:global": "mocha test/unit-global/*",
"test:single": "cross-env METAMASK_ENV=test mocha --require test/helper.js",
Switch from `npm` to `yarn` (#6843) As a solution to the constant lockfile churn issues we've had with `npm`, the project now uses `yarn` to manage dependencies. The `package-lock.json` file has been replaced with `yarn.lock`, which was created using `yarn import`. It should approximate the contents of `package-lock.json` fairly well, though there may be some changes due to deduplication. The codeowners file has been updated to reference this new lockfile. All documentation and npm scripts have been updated to reference `yarn` rather than `npm`. Note that running scripts using `npm run` still works fine, but it seemed better to switch those to `yarn` as well to avoid confusion. The `npm-audit` Bash script has been replaced with `yarn-audit`. The output of `yarn audit` is a bit different than `npm audit` in that it returns a bitmask to describe which severity issues were found. This made it simpler to check the results directly from the Bash script, so the associated `npm-audit-check.js` script was no longer required. The output should be exactly the same, and the information is still sourced from the same place (the npm registry). The new `yarn-audit` script does have an external dependency: `jq`. However, `jq` is already assumed to be present by another CI script, and is present on all CI images we use. `jq` was not added to `package.json` as a dependency because there is no official package on the npm registry, just wrapper scripts. We don't need it anywhere exept on CI anyway. The section in `CONTRIBUTING` about how to develop inside the `node_modules` folder was removed, as the advice was a bit dated, and wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
"test:integration": "yarn test:integration:build && yarn test:flat",
"test:integration:build": "gulp build:scss",
2019-07-03 03:49:59 +02:00
"test:e2e:chrome": "SELENIUM_BROWSER=chrome test/e2e/run-all.sh",
"test:web3:chrome": "SELENIUM_BROWSER=chrome test/e2e/run-web3.sh",
"test:web3:firefox": "SELENIUM_BROWSER=firefox test/e2e/run-web3.sh",
"test:e2e:firefox": "SELENIUM_BROWSER=firefox test/e2e/run-all.sh",
"test:coverage": "nyc --reporter=text --reporter=html npm run test:unit",
"test:coveralls-upload": "if [ $COVERALLS_REPO_TOKEN ]; then nyc report --reporter=text-lcov | coveralls; fi",
Switch from `npm` to `yarn` (#6843) As a solution to the constant lockfile churn issues we've had with `npm`, the project now uses `yarn` to manage dependencies. The `package-lock.json` file has been replaced with `yarn.lock`, which was created using `yarn import`. It should approximate the contents of `package-lock.json` fairly well, though there may be some changes due to deduplication. The codeowners file has been updated to reference this new lockfile. All documentation and npm scripts have been updated to reference `yarn` rather than `npm`. Note that running scripts using `npm run` still works fine, but it seemed better to switch those to `yarn` as well to avoid confusion. The `npm-audit` Bash script has been replaced with `yarn-audit`. The output of `yarn audit` is a bit different than `npm audit` in that it returns a bitmask to describe which severity issues were found. This made it simpler to check the results directly from the Bash script, so the associated `npm-audit-check.js` script was no longer required. The output should be exactly the same, and the information is still sourced from the same place (the npm registry). The new `yarn-audit` script does have an external dependency: `jq`. However, `jq` is already assumed to be present by another CI script, and is present on all CI images we use. `jq` was not added to `package.json` as a dependency because there is no official package on the npm registry, just wrapper scripts. We don't need it anywhere exept on CI anyway. The section in `CONTRIBUTING` about how to develop inside the `node_modules` folder was removed, as the advice was a bit dated, and wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
"test:flat": "yarn test:flat:build && karma start test/flat.conf.js",
"test:flat:build": "yarn test:flat:build:ui && yarn test:flat:build:tests && yarn test:flat:build:locales",
"test:flat:build:tests": "node test/integration/index.js",
"test:flat:build:states": "node development/genStates.js",
"test:flat:build:locales": "mkdirp dist/chrome && cp -R app/_locales dist/chrome/_locales",
Switch from `npm` to `yarn` (#6843) As a solution to the constant lockfile churn issues we've had with `npm`, the project now uses `yarn` to manage dependencies. The `package-lock.json` file has been replaced with `yarn.lock`, which was created using `yarn import`. It should approximate the contents of `package-lock.json` fairly well, though there may be some changes due to deduplication. The codeowners file has been updated to reference this new lockfile. All documentation and npm scripts have been updated to reference `yarn` rather than `npm`. Note that running scripts using `npm run` still works fine, but it seemed better to switch those to `yarn` as well to avoid confusion. The `npm-audit` Bash script has been replaced with `yarn-audit`. The output of `yarn audit` is a bit different than `npm audit` in that it returns a bitmask to describe which severity issues were found. This made it simpler to check the results directly from the Bash script, so the associated `npm-audit-check.js` script was no longer required. The output should be exactly the same, and the information is still sourced from the same place (the npm registry). The new `yarn-audit` script does have an external dependency: `jq`. However, `jq` is already assumed to be present by another CI script, and is present on all CI images we use. `jq` was not added to `package.json` as a dependency because there is no official package on the npm registry, just wrapper scripts. We don't need it anywhere exept on CI anyway. The section in `CONTRIBUTING` about how to develop inside the `node_modules` folder was removed, as the advice was a bit dated, and wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
"test:flat:build:ui": "yarn test:flat:build:states && browserify --transform babelify --transform brfs ./development/mock-dev.js -o ./development/bundle.js",
"ganache:start": "./development/run-ganache",
"sentry:publish": "node ./development/sentry-publish.js",
"lint": "eslint . --ext js,json",
"lint:fix": "eslint . --ext js,json --fix",
"lint:changed": "{ git ls-files --others --exclude-standard ; git diff-index --name-only --diff-filter=d HEAD ; } | grep --regexp='[.]js$' --regexp='[.]json$' | tr '\\n' '\\0' | xargs -0 eslint",
"lint:changed:fix": "{ git ls-files --others --exclude-standard ; git diff-index --name-only --diff-filter=d HEAD ; } | grep --regexp='[.]js$' --regexp='[.]json$' | tr '\\n' '\\0' | xargs -0 eslint --fix",
"verify-locales": "node ./development/verify-locale-strings.js",
2018-09-26 02:44:57 +02:00
"mozilla-lint": "addons-linter dist/firefox",
"watch": "cross-env METAMASK_ENV=test mocha --watch --require test/setup.js --reporter min --recursive \"test/unit/**/*.js\" \"ui/app/**/*.test.js\"",
"devtools:react": "react-devtools",
"devtools:redux": "remotedev --hostname=localhost --port=8000",
Switch from `npm` to `yarn` (#6843) As a solution to the constant lockfile churn issues we've had with `npm`, the project now uses `yarn` to manage dependencies. The `package-lock.json` file has been replaced with `yarn.lock`, which was created using `yarn import`. It should approximate the contents of `package-lock.json` fairly well, though there may be some changes due to deduplication. The codeowners file has been updated to reference this new lockfile. All documentation and npm scripts have been updated to reference `yarn` rather than `npm`. Note that running scripts using `npm run` still works fine, but it seemed better to switch those to `yarn` as well to avoid confusion. The `npm-audit` Bash script has been replaced with `yarn-audit`. The output of `yarn audit` is a bit different than `npm audit` in that it returns a bitmask to describe which severity issues were found. This made it simpler to check the results directly from the Bash script, so the associated `npm-audit-check.js` script was no longer required. The output should be exactly the same, and the information is still sourced from the same place (the npm registry). The new `yarn-audit` script does have an external dependency: `jq`. However, `jq` is already assumed to be present by another CI script, and is present on all CI images we use. `jq` was not added to `package.json` as a dependency because there is no official package on the npm registry, just wrapper scripts. We don't need it anywhere exept on CI anyway. The section in `CONTRIBUTING` about how to develop inside the `node_modules` folder was removed, as the advice was a bit dated, and wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
"start:dev": "concurrently -k -n build,react,redux yarn:start yarn:devtools:react yarn:devtools:redux",
"announce": "node development/announcer.js",
"version:bump": "node development/run-version-bump.js",
"storybook": "start-storybook -p 6006 -c .storybook",
"update-changelog": "./development/auto-changelog.sh",
"rollback": "./development/rollback.sh"
},
3box integration 2.0 (#6972) * Adds threebox controller * Adds threebox approval modal * Fix unit tests and lint after addition of threebox * Correct threebox behaviour after rejecting request for backup; fixes e2e tests. * Update threebox controller for automatic syncing * Ensure frontend locale updates when preferences are changed via direct update within controller * Add toggle in settings for 3box syncing * Update threebox controller for latest 3box version * Delete unnecessary frontend changes for threebox integration * Backing up address book contacts with threebox * Update unit tests for 3box-integration additions * Only enable threebox by default for new wallets * Mock globals for correct unit tests * 3box '1.10.2' -> '^1.10.2' * Correct capilalization on 3Box * Use log.debug instead of console.log in threebox controller * Update yarn.lock * Remove edge build * Split 3box module into background deps js file * extra bundle opts for bg-libs * sync yarn.lock * new3Box logic * Show confirm threebox restore after import * Remove bg-libs.js from manifest file for dev builds * Switch 3Box controller to using the spaces api (instead of the profile api) * Finalize switching to spaces api and only restoring from 3box after import * Update metamask-controller-test.js for threebox controller changes * Make threebox modal style consistent with others and update success button wording * Use mock 3box when in test * Correct 3box modal header * Remove unnecessary property of threebox controller provider * Remove unnecessary method calls after restoration from 3box in the threebox-restore-confirm modal. * Replace setThreeBoxSyncingPermission calls in routes/index.js with turnThreeBoxSyncingOn * Replace erroneous use of with * Replace erroneous use of threeboxSyncing with threeBoxSyncingAllowed in advancted-tab directory * Lint fixes for 3box changes * Log errors encountered when updating 3Box * Remove unnecessary parameter from state update * Add timeout to initial 3Box sync The initial 3Box sync will now timeout after 1 minute. If the timeout is triggered, 3Box is disabled and cannot be re-enabled unless the initial sync does finally finish. If it never finishes, 3Box cannot be enabled unless the extension is reinstalled. The Advanced Settings page was updated to show this option as disabled in that circumstance, with a new discription explaining why it's disabled. The UI here could certainly be improved. Additionally, "on" and "off" labels were added to the toggle to match the other toggles on the Advanced Settings page. * Use non-minified 3Box module We had previously used the minified 3Box module to avoid a build error encountered when `envify` was processing the `libp2p` module (which is used by 3Box). The build would fail because `esprima` (used by `envify`) is incompatible with the object spread/rest operator (which is used in `libp2p`). That issue has been solved by adding a global Babelify transformation specifically for transpiling out the object rest/spread operator from dependencies. It has been targetted to only affect `libp2p` to avoid extending the build time too much. This workaround can be used until a new version of `esprima` is released that includes this bug fix. * Use app key addresses for threebox * Replace use of modal for confirming 3box restoration with a home notification * Adds e2e tests for restoring from threebox * Update eth-keyring-controller to 5.1.0 * Correct parameters passed to getAppKeyAddress in threebox.js * Add prefix to origin passed to getAppKeyAddress in threebox.js * Remove unused locale message. * Prevent CORS errors in firefox e2e tests * Ensure extraneous scripts are excluded from the local test dev build * Move threeBoxLastUpdate state from home.component to redux * Threebox PR code cleanup * Always use first address when initializing threebox * Replace setRestoredFromThreeBox api with setRestoredFromThreeBoxToFalse and setRestoredFromThreeBoxToTrue * Update development/metamaskbot-build-announce.js to include ui-libs and bg-libs in hard coded bundle list * Update test/e2e/threebox.spec.js to use new helpers added with pull #7144 * Make setFeatureFlag available on the ui window during testing * Hide threebox feature behind a feature flag that can only be activated via dev console * Remove unnecessary migration of threebox feature flag * Prevent this.init() call in threebox constructor if feature flag is not turned on * Prevent threebox notification from showing if feature flag is falsy * http://localhost/8889 -> http://localhost/* in gulp manifest:testing tasks
2019-09-16 19:11:01 +02:00
"resolutions": {
"3box/ipfs/ipld-zcash/zcash-bitcore-lib/lodash": "^4.17.12",
"pubnub/superagent-proxy": "^2.0.0"
3box integration 2.0 (#6972) * Adds threebox controller * Adds threebox approval modal * Fix unit tests and lint after addition of threebox * Correct threebox behaviour after rejecting request for backup; fixes e2e tests. * Update threebox controller for automatic syncing * Ensure frontend locale updates when preferences are changed via direct update within controller * Add toggle in settings for 3box syncing * Update threebox controller for latest 3box version * Delete unnecessary frontend changes for threebox integration * Backing up address book contacts with threebox * Update unit tests for 3box-integration additions * Only enable threebox by default for new wallets * Mock globals for correct unit tests * 3box '1.10.2' -> '^1.10.2' * Correct capilalization on 3Box * Use log.debug instead of console.log in threebox controller * Update yarn.lock * Remove edge build * Split 3box module into background deps js file * extra bundle opts for bg-libs * sync yarn.lock * new3Box logic * Show confirm threebox restore after import * Remove bg-libs.js from manifest file for dev builds * Switch 3Box controller to using the spaces api (instead of the profile api) * Finalize switching to spaces api and only restoring from 3box after import * Update metamask-controller-test.js for threebox controller changes * Make threebox modal style consistent with others and update success button wording * Use mock 3box when in test * Correct 3box modal header * Remove unnecessary property of threebox controller provider * Remove unnecessary method calls after restoration from 3box in the threebox-restore-confirm modal. * Replace setThreeBoxSyncingPermission calls in routes/index.js with turnThreeBoxSyncingOn * Replace erroneous use of with * Replace erroneous use of threeboxSyncing with threeBoxSyncingAllowed in advancted-tab directory * Lint fixes for 3box changes * Log errors encountered when updating 3Box * Remove unnecessary parameter from state update * Add timeout to initial 3Box sync The initial 3Box sync will now timeout after 1 minute. If the timeout is triggered, 3Box is disabled and cannot be re-enabled unless the initial sync does finally finish. If it never finishes, 3Box cannot be enabled unless the extension is reinstalled. The Advanced Settings page was updated to show this option as disabled in that circumstance, with a new discription explaining why it's disabled. The UI here could certainly be improved. Additionally, "on" and "off" labels were added to the toggle to match the other toggles on the Advanced Settings page. * Use non-minified 3Box module We had previously used the minified 3Box module to avoid a build error encountered when `envify` was processing the `libp2p` module (which is used by 3Box). The build would fail because `esprima` (used by `envify`) is incompatible with the object spread/rest operator (which is used in `libp2p`). That issue has been solved by adding a global Babelify transformation specifically for transpiling out the object rest/spread operator from dependencies. It has been targetted to only affect `libp2p` to avoid extending the build time too much. This workaround can be used until a new version of `esprima` is released that includes this bug fix. * Use app key addresses for threebox * Replace use of modal for confirming 3box restoration with a home notification * Adds e2e tests for restoring from threebox * Update eth-keyring-controller to 5.1.0 * Correct parameters passed to getAppKeyAddress in threebox.js * Add prefix to origin passed to getAppKeyAddress in threebox.js * Remove unused locale message. * Prevent CORS errors in firefox e2e tests * Ensure extraneous scripts are excluded from the local test dev build * Move threeBoxLastUpdate state from home.component to redux * Threebox PR code cleanup * Always use first address when initializing threebox * Replace setRestoredFromThreeBox api with setRestoredFromThreeBoxToFalse and setRestoredFromThreeBoxToTrue * Update development/metamaskbot-build-announce.js to include ui-libs and bg-libs in hard coded bundle list * Update test/e2e/threebox.spec.js to use new helpers added with pull #7144 * Make setFeatureFlag available on the ui window during testing * Hide threebox feature behind a feature flag that can only be activated via dev console * Remove unnecessary migration of threebox feature flag * Prevent this.init() call in threebox constructor if feature flag is not turned on * Prevent threebox notification from showing if feature flag is falsy * http://localhost/8889 -> http://localhost/* in gulp manifest:testing tasks
2019-09-16 19:11:01 +02:00
},
2015-08-01 03:38:02 +02:00
"dependencies": {
"3box": "^1.10.2",
"@babel/runtime": "^7.5.5",
"@material-ui/core": "1.0.0",
"@sentry/browser": "^4.1.1",
2018-08-17 18:56:07 +02:00
"@zxing/library": "^0.8.0",
2019-06-05 20:05:01 +02:00
"abi-decoder": "^1.2.0",
"abortcontroller-polyfill": "^1.3.0",
"asmcrypto.js": "^2.3.2",
"await-semaphore": "^0.1.1",
"bignumber.js": "^4.1.0",
2016-10-28 01:50:01 +02:00
"bip39": "^2.2.0",
"bluebird": "^3.5.0",
2017-08-04 20:42:13 +02:00
"bn.js": "^4.11.7",
"boron": "^0.2.3",
2016-12-20 19:11:51 +01:00
"browser-passworder": "^2.0.3",
2016-04-20 22:22:41 +02:00
"browserify-derequire": "^0.9.4",
"browserify-unibabel": "^3.0.0",
"c3": "^0.6.7",
2017-08-23 13:04:11 +02:00
"classnames": "^2.2.5",
"clone": "^2.1.2",
2019-10-31 19:37:06 +01:00
"content-hash": "^2.4.4",
2017-08-04 01:38:44 +02:00
"copy-to-clipboard": "^3.0.8",
2018-04-03 22:52:01 +02:00
"currency-formatter": "^1.4.2",
"d3": "^5.7.0",
"debounce": "1.1.0",
"debounce-stream": "^2.0.0",
"deep-extend": "^0.5.1",
"deep-freeze-strict": "1.1.1",
2017-05-15 23:35:24 +02:00
"detect-node": "^2.0.3",
"detectrtc": "^1.3.6",
2016-01-15 11:03:42 +01:00
"dnode": "^1.2.2",
2016-01-17 10:27:25 +01:00
"end-of-stream": "^1.1.0",
"eth-block-tracker": "^4.4.2",
2019-11-14 02:05:56 +01:00
"eth-contract-metadata": "1.9.3",
2018-07-27 02:24:39 +02:00
"eth-ens-namehash": "^2.0.8",
2019-09-17 18:36:09 +02:00
"eth-json-rpc-errors": "^1.1.0",
"eth-json-rpc-filters": "^4.1.1",
"eth-json-rpc-infura": "^4.0.1",
"eth-json-rpc-middleware": "^4.2.0",
"eth-keyring-controller": "^5.3.0",
"eth-ledger-bridge-keyring": "^0.2.0",
"eth-method-registry": "^1.2.0",
2017-08-04 23:11:40 +02:00
"eth-phishing-detect": "^1.1.4",
2017-06-15 06:42:29 +02:00
"eth-query": "^2.1.2",
"eth-sig-util": "^2.3.0",
"eth-token-tracker": "^1.1.10",
"eth-trezor-keyring": "^0.4.0",
2017-09-29 02:39:53 +02:00
"ethereumjs-abi": "^0.6.4",
2019-06-11 17:24:47 +02:00
"ethereumjs-tx": "1.3.7",
"ethereumjs-util": "5.1.0",
2016-10-21 01:44:31 +02:00
"ethereumjs-wallet": "^0.6.0",
2017-10-14 17:23:44 +02:00
"etherscan-link": "^1.0.2",
"ethjs": "^0.4.0",
"ethjs-contract": "^0.2.3",
"ethjs-ens": "^2.0.0",
"ethjs-query": "^0.3.4",
"extension-port-stream": "^1.0.0",
"extensionizer": "^1.0.1",
"fast-json-patch": "^2.0.4",
"fuse.js": "^3.2.0",
2019-11-06 17:03:49 +01:00
"gaba": "^1.8.0",
"human-standard-token-abi": "^2.0.0",
2016-10-28 01:01:21 +02:00
"jazzicon": "^1.2.0",
"json-rpc-engine": "^5.1.5",
2019-06-05 20:05:01 +02:00
"json-rpc-middleware-stream": "^2.1.1",
2018-09-10 23:11:57 +02:00
"jsonschema": "^1.2.4",
2017-08-30 11:05:45 +02:00
"lodash.debounce": "^4.0.8",
"lodash.shuffle": "^4.2.0",
2017-02-20 21:59:44 +01:00
"loglevel": "^1.4.1",
"luxon": "^1.8.2",
"metamask-inpage-provider": "^3.0.0",
"metamask-logo": "^2.1.4",
2017-01-10 22:46:15 +01:00
"mkdirp": "^0.5.1",
2018-07-27 02:24:39 +02:00
"multihashes": "^0.4.12",
"nonce-tracker": "^1.0.0",
2017-05-23 00:43:20 +02:00
"number-to-bn": "^1.7.0",
"obj-multiplex": "^1.0.0",
"obs-store": "^4.0.3",
"percentile": "^1.2.0",
"pify": "^3.0.0",
2016-04-18 20:31:06 +02:00
"polyfill-crypto.getrandomvalues": "^1.0.0",
2017-07-19 00:41:30 +02:00
"post-message-stream": "^3.0.0",
2016-11-29 23:56:02 +01:00
"promise-filter": "^1.1.0",
"promise-to-callback": "^1.0.0",
2018-03-27 09:20:35 +02:00
"prop-types": "^15.6.1",
"pubnub": "4.24.4",
2018-03-09 20:51:03 +01:00
"pump": "^3.0.0",
"punycode": "^2.1.1",
2019-02-25 20:10:13 +01:00
"qrcode-generator": "1.4.1",
"ramda": "^0.24.1",
2017-11-27 20:49:49 +01:00
"react": "^15.6.2",
"react-dnd": "^3.0.2",
"react-dnd-html5-backend": "^7.4.4",
2017-11-27 20:49:49 +01:00
"react-dom": "^15.6.2",
2017-07-19 00:41:30 +02:00
"react-hyperscript": "^3.0.0",
"react-idle-timer": "^4.2.5",
2018-09-10 23:11:57 +02:00
"react-inspector": "^2.3.0",
"react-media": "^1.8.0",
2017-07-19 00:41:30 +02:00
"react-redux": "^5.0.5",
"react-router-dom": "^4.2.2",
2017-11-24 02:33:44 +01:00
"react-select": "^1.0.0",
"react-simple-file-input": "^2.0.0",
"react-tippy": "^1.2.2",
"react-toggle-button": "^2.2.0",
2016-06-30 00:57:59 +02:00
"react-tooltip-component": "^0.3.0",
"react-transition-group": "^1.2.1",
2017-10-03 23:43:11 +02:00
"react-trigger-change": "^1.0.2",
2017-11-24 02:33:44 +01:00
"reactify": "^1.1.1",
"readable-stream": "^2.3.3",
2017-08-21 13:56:09 +02:00
"recompose": "^0.25.0",
"redux": "^3.0.5",
2017-07-19 00:41:30 +02:00
"redux-logger": "^3.0.6",
"redux-thunk": "^2.2.0",
2017-09-22 19:41:14 +02:00
"request-promise": "^4.2.1",
"reselect": "^3.0.1",
"safe-event-emitter": "^1.0.1",
2019-01-22 19:23:11 +01:00
"single-call-balance-checker-abi": "^1.0.0",
"string.prototype.matchall": "^3.0.1",
"swappable-obj-proxy": "^1.1.0",
"textarea-caret": "^3.0.1",
2016-12-21 01:41:04 +01:00
"valid-url": "^1.0.9",
2019-06-05 20:05:01 +02:00
"web3": "^0.20.7",
"web3-stream-provider": "^4.0.0",
"webrtc-adapter": "^6.3.0",
2018-07-27 02:24:39 +02:00
"xtend": "^4.0.1"
2015-08-01 03:38:02 +02:00
},
"devDependencies": {
"@babel/core": "^7.5.5",
"@babel/plugin-proposal-class-properties": "^7.5.5",
"@babel/plugin-proposal-object-rest-spread": "^7.5.5",
"@babel/plugin-transform-runtime": "^7.5.5",
"@babel/preset-env": "^7.5.5",
"@babel/preset-react": "^7.0.0",
"@babel/register": "^7.5.5",
"@sentry/cli": "^1.30.3",
"@storybook/addon-actions": "^5.2.6",
"@storybook/addon-info": "^5.1.1",
"@storybook/addon-knobs": "^3.4.2",
"@storybook/react": "^5.1.1",
"addons-linter": "1.14.0",
"babel-eslint": "^10.0.2",
"babelify": "^10.0.0",
"brfs": "^1.6.1",
2018-12-06 16:16:05 +01:00
"browserify": "^16.2.3",
"browserify-transform-tools": "^1.7.0",
2017-07-19 00:41:30 +02:00
"chai": "^4.1.0",
2018-08-06 18:16:39 +02:00
"chromedriver": "^2.41.0",
"concurrently": "^4.1.1",
"coveralls": "^3.0.0",
"cross-env": "^5.1.4",
"css-loader": "^2.1.1",
2017-07-19 00:41:30 +02:00
"del": "^3.0.0",
"deps-dump": "^1.1.0",
2017-04-05 19:24:30 +02:00
"envify": "^4.0.0",
"enzyme": "^3.4.4",
"enzyme-adapter-react-15": "^1.0.6",
"eslint": "^6.0.1",
2017-05-04 23:34:25 +02:00
"eslint-plugin-chai": "0.0.1",
"eslint-plugin-import": "^2.18.2",
2018-04-02 23:47:47 +02:00
"eslint-plugin-json": "^1.2.0",
"eslint-plugin-mocha": "^5.0.0",
2017-11-02 13:15:59 +01:00
"eslint-plugin-react": "^7.4.0",
"fetch-mock": "^6.5.2",
"file-loader": "^1.1.11",
2018-08-17 18:56:07 +02:00
"fs-extra": "^6.0.1",
2017-08-09 02:46:09 +02:00
"fs-promise": "^2.0.3",
"ganache-cli": "^6.4.4",
"ganache-core": "2.8.0",
2019-06-05 20:05:01 +02:00
"geckodriver": "^1.16.2",
"gh-pages": "^1.2.0",
"gulp": "^4.0.0",
"gulp-autoprefixer": "^5.0.0",
"gulp-babel": "^7.0.0",
"gulp-debug": "^3.2.0",
"gulp-eslint": "^4.0.0",
"gulp-imagemin": "^6.1.0",
"gulp-json-editor": "^2.2.1",
"gulp-livereload": "4.0.0",
"gulp-multi-process": "^1.3.1",
"gulp-rename": "^1.4.0",
2017-07-19 00:41:30 +02:00
"gulp-replace": "^0.6.1",
"gulp-rtlcss": "^1.4.0",
"gulp-sass": "^4.0.0",
2017-07-19 00:41:30 +02:00
"gulp-sourcemaps": "^2.6.0",
"gulp-stylelint": "^7.0.0",
2019-09-10 19:02:48 +02:00
"gulp-terser-js": "^5.0.0",
2016-03-03 08:29:43 +01:00
"gulp-util": "^3.0.7",
2019-06-05 20:05:01 +02:00
"gulp-watch": "^5.0.1",
2017-07-19 00:41:30 +02:00
"gulp-zip": "^4.0.0",
"http-server": "^0.11.1",
2017-01-10 21:39:01 +01:00
"isomorphic-fetch": "^2.2.1",
2019-06-05 20:05:01 +02:00
"jsdoc": "^3.6.2",
2017-09-12 23:14:24 +02:00
"jsdom": "^11.2.0",
2017-07-19 00:41:30 +02:00
"jsdom-global": "^3.0.2",
"karma": "^4.1.0",
"karma-chrome-launcher": "^2.2.0",
"karma-cli": "^1.0.1",
"karma-firefox-launcher": "^1.0.1",
"karma-qunit": "^1.2.1",
2016-03-03 08:29:43 +01:00
"lodash.assign": "^4.0.6",
"mocha": "^5.0.0",
2017-07-19 00:41:30 +02:00
"mocha-eslint": "^4.0.0",
"mocha-jsdom": "^1.1.0",
2017-07-19 00:41:30 +02:00
"mocha-sinon": "^2.0.0",
"nock": "^9.0.14",
2019-06-05 20:05:01 +02:00
"node-sass": "^4.12.0",
"nyc": "^13.0.0",
"path": "^0.12.7",
2018-08-17 18:56:07 +02:00
"prepend-file": "^1.3.1",
"proxyquire": "2.0.1",
2016-07-01 03:22:16 +02:00
"qs": "^6.2.0",
2017-11-27 20:49:49 +01:00
"qunitjs": "^2.4.1",
"radgrad-jsdoc-template": "^1.1.3",
"react-devtools": "^3.6.1",
2017-11-27 20:49:49 +01:00
"react-test-renderer": "^15.6.2",
"read-installed": "^4.0.3",
2018-07-08 03:53:00 +02:00
"redux-mock-store": "^1.5.3",
"redux-test-utils": "^0.2.2",
"remote-redux-devtools": "^0.5.16",
"remotedev-server": "^0.3.1",
"resolve-url-loader": "^2.3.0",
"rimraf": "^2.6.2",
"sass-loader": "^7.0.1",
2018-03-29 08:12:41 +02:00
"selenium-webdriver": "^3.5.0",
"sesify": "^4.2.1",
"sesify-viz": "^3.0.5",
"sinon": "^5.0.0",
"source-map": "^0.7.2",
"source-map-explorer": "^2.0.1",
2018-08-06 18:08:41 +02:00
"static-server": "^2.2.1",
"style-loader": "^0.21.0",
Optimize images only during production build (#7194) * Optimize images only during production build Image optimization is fairly slow (over a minute), and isn't necessary for test or development builds. It is now only run as part of the `build` gulp task, which is used during `gulp dist`. * Remove unused gulp tasks There were two high-level tasks and one style formatting task that were not used by any npm scripts, so were probably unused generally. The `dev` task was a duplcate of `dev:extension`. The `build:extension` task was useful for just building the extension without performing other steps required by the final production bundle, but it was broken. It didn't correctly build the ui-libs and bg-libs required. Instead of fixing it, it has been removed until the handling of those separate library bundles is simplified. The style formatting task seems like it could be useful, but I'm unsure about keeping it around as opt-in, as in practice it'll just end up being ignored. Moreover the library authors themselves are recommending switching to `prettier`, so I think we're better off removing it for now, then considering using `prettier` if we want to introduce something like this again. The stylelint dependency was added because it's a peer dependency of gulp-stylelint that should have already been listed among our dependencies. It hadn't caused a problem before because it happened to be a transitive dependency of gulp-stylefmt, which is no longer needed and has been removed.
2019-09-21 18:32:17 +02:00
"stylelint": "^9.10.1",
"stylelint-config-standard": "^18.2.0",
2019-06-05 20:05:01 +02:00
"testem": "^2.16.0",
"through2": "^2.0.3",
2018-01-04 13:40:38 +01:00
"vinyl-buffer": "^1.0.1",
"vinyl-source-stream": "^2.0.0",
2019-06-05 20:05:01 +02:00
"watchify": "^3.11.1"
2015-08-01 03:38:02 +02:00
},
"engines": {
Switch from `npm` to `yarn` (#6843) As a solution to the constant lockfile churn issues we've had with `npm`, the project now uses `yarn` to manage dependencies. The `package-lock.json` file has been replaced with `yarn.lock`, which was created using `yarn import`. It should approximate the contents of `package-lock.json` fairly well, though there may be some changes due to deduplication. The codeowners file has been updated to reference this new lockfile. All documentation and npm scripts have been updated to reference `yarn` rather than `npm`. Note that running scripts using `npm run` still works fine, but it seemed better to switch those to `yarn` as well to avoid confusion. The `npm-audit` Bash script has been replaced with `yarn-audit`. The output of `yarn audit` is a bit different than `npm audit` in that it returns a bitmask to describe which severity issues were found. This made it simpler to check the results directly from the Bash script, so the associated `npm-audit-check.js` script was no longer required. The output should be exactly the same, and the information is still sourced from the same place (the npm registry). The new `yarn-audit` script does have an external dependency: `jq`. However, `jq` is already assumed to be present by another CI script, and is present on all CI images we use. `jq` was not added to `package.json` as a dependency because there is no official package on the npm registry, just wrapper scripts. We don't need it anywhere exept on CI anyway. The section in `CONTRIBUTING` about how to develop inside the `node_modules` folder was removed, as the advice was a bit dated, and wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
"node": "^10.16.0",
"yarn": "^1.16.0"
2015-08-01 03:38:02 +02:00
}
}