TheDude
/
ciphermask
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
A Metamask fork with Infura removed and default networks editable
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9410 Commits
2 Branches
1 Tag
200 MiB
Tag: Branch: Tree: d7a4dfebeb
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd7a4dfebeb'
${ noResults }
ciphermask/package.json

297 lines
11 KiB
Raw Normal View History Unescape

init commit
9 years ago
{
major - migrate to blockapps-web3
9 years ago
"name": "metamask-crx",
init commit
9 years ago
"version": "0.0.0",
deps - add metamas-ui, bump provider-engine
9 years ago
"private": true,
migrate to new ui + provider
9 years ago
"scripts": {
npm scripts - rewrite default scripts to new task names
7 years ago
"start": "gulp dev:extension",
Add build step to mozilla-lint
6 years ago
"dist": "gulp dist",
Remove unused AppVeyor configuration (#6840) The AppVeyor configuration appears to be unused - this project is not connected to AppVeyor. After deleting the AppVeyor config, the JSDoc config was the last thing in the `development/tools` directory. That felt a little silly, so I moved it up to `development`.
5 years ago
"doc": "jsdoc -c development/.jsdoc.json",
Add jsdoc gh-pages script
6 years ago
"publish-docs": "gh-pages -d docs/jsdocs",
Use webRequest to cancel all requests to infura in e2e tests.
6 years ago
"start:test": "gulp dev:test",
ci: Add build:test Gulp task for e2e build
6 years ago
"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.
5 years ago
"test": "yarn test:unit && yarn lint",
Move e2e tests out of beta dir (#6785)
5 years ago
"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.
5 years ago
"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",
I5849 incremental account security (#6874) * Implements ability to defer seed phrase backup to later * Adds incremental-security.spec.js, including test dapp that sends signed tx with stand alone localhost provider * Update metamask-responsive-ui for incremental account security changes * Update backup-notification style and fix responsiveness of seed phrase screen * Remove uneeded files from send-eth-with-private-key-test/ * Apply linguist flags in .gitattributes for send-eth-with-private-key-test/ethereumjs-tx.js * Improve docs in controllers/onboarding.js * Clean up metamask-extension/test/e2e/send-eth-with-private-key-test/index.html * Remove unnecessary newlines in a couple first-time-flow/ files * Fix import of backup-notification in home.component * Fix git attrs file
5 years ago
"sendwithprivatedapp": "static-server test/e2e/send-eth-with-private-key-test --port 8080",
Remove dot-only-hunter from test:unit script
6 years ago
"test:unit": "cross-env METAMASK_ENV=test mocha --exit --require test/setup.js --recursive \"test/unit/**/*.js\" \"ui/app/**/*.test.js\"",
use 'cross-env' for env-variables within npm scripts, re #3426
7 years ago
"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.
5 years ago
"test:integration": "yarn test:integration:build && yarn test:flat",
test - breakout npm script for building for integration tests
7 years ago
"test:integration:build": "gulp build:scss",
Move e2e tests out of beta dir (#6785)
5 years ago
"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",
Make Coveralls its own optional CI job (#7002) * ci: Move Coveralls into optional step * Split Coveralls step out of test:coverage npm script
5 years ago
"test:coverage": "nyc --reporter=text --reporter=html npm run test:unit",
tests - refactor and rename npm scripts
7 years ago
"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.
5 years ago
"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",
tests - refactor and rename npm scripts
7 years ago
"test:flat:build:tests": "node test/integration/index.js",
"test:flat:build:states": "node development/genStates.js",
test - integration - add locale build step
7 years ago
"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.
5 years ago
"test:flat:build:ui": "yarn test:flat:build:states && browserify --transform babelify --transform brfs ./development/mock-dev.js -o ./development/bundle.js",
Replace deprecated shell-parallel with concurrently (#6807) * Replace shell-parallel with concurrently * Update ganache-cli
5 years ago
"ganache:start": "./development/run-ganache",
ci - job-publish - publish source+sourcemaps to sentry if new release
7 years ago
"sentry:publish": "node ./development/sentry-publish.js",
Lint `.json` files (#6852) We've been using the `eslint-plugin-json` plugin for some time, but we haven't been visiting `.json` files in the lint script. The lint script has now been updated to incude `.json` files, which means any invalid JSON will result in a lint error. Unfortunately this JSON plugin doesn't seem to apply the other eslint rules (such as `key-spacing`) to the JSON files. I wasn't able to find a way to get that to work. Instead I manually auto-formatted each of the locale `message.json` files, which fixed many whitespace inconsistencies. The `states.json` file was deleted completely, as it appears to be unused. It wasn't a valid JSON file anyway, it was JavaScript. It looks like a `states.js` file is automatically generated, but an old copy was accidentally saved as `states.json` and included in the repo. Many duplicate key errors were found and fixed in the `development/states/` JSON files. `package-lock.json` was added to `.eslintignore` because it was very slow to lint, and linting it doesn't provide much value.
5 years ago
"lint": "eslint . --ext js,json",
"lint:fix": "eslint . --ext js,json --fix",
Add lint:changed script entry to lint only changed files (#7055)
5 years ago
"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 on CI (#7199) * Add '--quiet' flag to verify locales script The `--quiet` flag reduces the console output to just the essential information for running in a CI environment. For each locale, it will print the number of unused messages (if any). * Add `verify-locales` script to lint CI job The locales are now verified as part of the lint CI job. Any unused messages detected will result in the job failing.
5 years ago
"verify-locales": "node ./development/verify-locale-strings.js",
add mozilla lint job
6 years ago
"mozilla-lint": "addons-linter dist/firefox",
Fix 'watch' npm script The `watch` npm script did not work - it must have gone unused for some time. The following changes were required for it to work: * Use the `--watch` flag, rather than the `watch` command (which appears to not exist) * Set the `METAMASK_ENV` environment variable to "test" * Include the tests in the `ui` directory * require the `test/setup.js` file before running the tests The reporter was also changed to `min`, which is generally recommended for use with the `--watch` flag.
6 years ago
"watch": "cross-env METAMASK_ENV=test mocha --watch --require test/setup.js --reporter min --recursive \"test/unit/**/*.js\" \"ui/app/**/*.test.js\"",
Add React and Redux DevTools (#6793) * Add React and Redux DevTools * Conditionally load react-devtools * Add start:dev npm script to run the app with devtools Co-Authored-By: Mark Stacey <markjstacey@gmail.com>
5 years ago
"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.
5 years ago
"start:dev": "concurrently -k -n build,react,redux yarn:start yarn:devtools:react yarn:devtools:redux",
Add ability to show notices to user & get confirmation. Implement generation of markdown for notice files. Create npm command. Enhance notice generation. Add test files to test multiple notices. Add basic markdown support to notices. Interval checks for updates. Add extensionizer and linker Add terms and conditions state file Add link support to disclaimer. Changelog addition.
8 years ago
"announce": "node development/announcer.js",
Add version bumping script One step towards automating our deploy process is automating our version bumping scheme. This PR does that.
7 years ago
"version:bump": "node development/run-version-bump.js",
provide automatic changelog since last tag for linux
6 years ago
"storybook": "start-storybook -p 6006 -c .storybook",
Add rollback script, move auto-changelog script (#6252)
6 years ago
"update-changelog": "./development/auto-changelog.sh",
"rollback": "./development/rollback.sh"
Move UI deps into main plugin package.json Also move UI test scripts into main plugin Also move testing explanation to main plugin README.
9 years ago
},
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
5 years ago
"resolutions": {
"3box/ipfs/ipld-zcash/zcash-bitcore-lib/lodash": "^4.17.12"
},
init commit
9 years ago
"dependencies": {
Remove unused locale messages (#7190) * Switch to using string literals for locale keys Various message keys were being specified with a string template instead of a string literal. They have been switched to use string literals so that the script for detecting unused messages can find them. * Remove unused locale messages A number of unused locale messages have been removed - probably leftover from old UI elements that have since been removed. The `verify_locale_strings` script has been augmented to search the UI for string literals, and match those against the locale message keys in the `en` locale. Any messages without a corresponding string literal are assumed to be unused. The script has also been updated with an optional `--fix` parameter, which will automatically delete any unused messages from locales. 148 unused messages were found in this case, out of a total of about 650 messages. Another 70 messages are _potentially_ unused and require further investigation, but weren't as easy to rule out because they were found in string literals. * Remove additional unused locale messages The following messages were more difficult to rule out because they were present as string literals in the UI. They do appear to be unused as locale keys though.
5 years ago
"3box": "^1.10.2",
Upgrade to Babel 7 (#6942) Babel 7 moved to a new configuration format, and they've scoped all of their packages under `@babel/`. This brings MetaMask in-line with dependencies we use that _already_ use Babel 7, and it eliminates a few unfortunate edge cases that can prevent dependencies from being correctly transpiled.
5 years ago
"@babel/runtime": "^7.5.5",
Reestablish old versions of eth-keyring-controller and eth-hd-keyring
6 years ago
"@material-ui/core": "1.0.0",
sentry - replace raven-js with sentry/browser
6 years ago
"@sentry/browser": "^4.1.1",
fix merge conflicts
6 years ago
"@zxing/library": "^0.8.0",
npm audit fix
6 years ago
"abi-decoder": "^1.2.0",
Add polyfill for AbortController (#7157) The AbortController is used in both the background and the UI. Support for AbortController was added to Chrome in version 66, which is above our minimum supported version. I did consider increasing the minimum Chrome version to 66, but we have a decent number of users still on Chrome 65 unfortunately.
5 years ago
"abortcontroller-polyfill": "^1.3.0",
Update asmcrypto.js to latest version (#6767) This silences a warning message that was printed to the console whenever this module was loaded during tests. The API changes between these two versions were reviewed carefully for differences. The only difference made was to `PBKDF2_HMAC_SHA256.bytes`, which was replaced by `Pbkdf2HmacSha256`. The length argument no longer has a default value, so it has been set to match what the default value was in the previous version we used, which is 32 (the SHA256 hash size).
5 years ago
"asmcrypto.js": "^2.3.2",
nonce-tracker - fix lock mechanism to be a real mutex
7 years ago
"await-semaphore": "^0.1.1",
toggle wired up to preferences property store
7 years ago
"bignumber.js": "^4.1.0",
Add hd wallet keyring
8 years ago
"bip39": "^2.2.0",
tests - unit - fail on unhandled promise rejection
8 years ago
"bluebird": "^3.5.0",
bring your own BN
7 years ago
"bn.js": "^4.11.7",
[WIP] Add packages and tasks for linting scss
7 years ago
"boron": "^0.2.3",
Bump passworder version
8 years ago
"browser-passworder": "^2.0.3",
build - post process with dereq
9 years ago
"browserify-derequire": "^0.9.4",
add browserify-unibabel to package.json
7 years ago
"browserify-unibabel": "^3.0.0",
Adds not yet functional gas price chart.
6 years ago
"c3": "^0.6.7",
Add BackupPhraseScreen
7 years ago
"classnames": "^2.2.5",
sentry - include app state in ui errors
6 years ago
"clone": "^2.1.2",
Resolve onion addresses (#6869) * Resolve onion address * npm i content-hash@latest
5 years ago
"content-hash": "^2.4.3",
deps - update
7 years ago
"copy-to-clipboard": "^3.0.8",
Internationalize currency Fixes #3580
7 years ago
"currency-formatter": "^1.4.2",
Adds not yet functional gas price chart.
6 years ago
"d3": "^5.7.0",
Debounce was breaking in update As found in issue here: https://github.com/MetaMask/metamask-extension/issues/5064 Pinned the version at 1.1.0 until the new version with breaking changes can be intergrated.
6 years ago
"debounce": "1.1.0",
Debounce storage to avoid crashing pump
7 years ago
"debounce-stream": "^2.0.0",
Merge branch 'develop' into i3725-refactor-send-component-
7 years ago
"deep-extend": "^0.5.1",
Skip jazzicons in unit tests
8 years ago
"detect-node": "^2.0.3",
added crossbrowser support and error handling
6 years ago
"detectrtc": "^1.3.6",
integrate metamask-ui with id mgmt
9 years ago
"dnode": "^1.2.2",
refactor - push data to popup
9 years ago
"end-of-stream": "^1.1.0",
Remove Babel 6 from internal dependencies (#7037) remove babel@6 from internal deps update internal deps to latest published versions
5 years ago
"eth-block-tracker": "^4.4.2",
Update eth-contract-metadata to use published registry version (#6784)
5 years ago
"eth-contract-metadata": "^1.9.2",
working without permission issues
6 years ago
"eth-ens-namehash": "^2.0.8",
add user rejected errors
5 years ago
"eth-json-rpc-errors": "^1.1.0",
Remove Babel 6 from internal dependencies (#7037) remove babel@6 from internal deps update internal deps to latest published versions
5 years ago
"eth-json-rpc-filters": "^4.1.0",
"eth-json-rpc-infura": "^4.0.1",
Bump eth-json-rpc-middleware dependency (#7128) * Update eth-json-rpc-middleware to @^4.2.0 * Resolve all eth-json-rpc-middleware to 4.2.0
5 years ago
"eth-json-rpc-middleware": "^4.2.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
5 years ago
"eth-keyring-controller": "^5.1.0",
npm audit: Works with eth-ledger-bridge-keyring
6 years ago
"eth-ledger-bridge-keyring": "^0.2.0",
Update to eth-method-registry@1.2.0 (#6403)
6 years ago
"eth-method-registry": "^1.2.0",
blacklist - bump phishing detector
7 years ago
"eth-phishing-detect": "^1.1.4",
bump eth-query for quiter logs
8 years ago
"eth-query": "^2.1.2",
Bump eth-sig-util to 2.3.0 (#6896) * Bump eth-sig-util to 2.3.0 * Bump eth-keyring-controller to 4.x
5 years ago
"eth-sig-util": "^2.3.0",
Remove Babel 6 from internal dependencies (#7037) remove babel@6 from internal deps update internal deps to latest published versions
5 years ago
"eth-token-tracker": "^1.1.10",
npm audit: Works with eth-trezor-keyring
6 years ago
"eth-trezor-keyring": "^0.4.0",
Query for gas estimates
7 years ago
"ethereumjs-abi": "^0.6.4",
pin ethereumjs-tx (#6706)
6 years ago
"ethereumjs-tx": "1.3.7",
deps - update
7 years ago
"ethereumjs-util": "github:ethereumjs/ethereumjs-util#ac5d0908536b447083ea422b435da27f26615de9",
Began adding first basic keyring
8 years ago
"ethereumjs-wallet": "^0.6.0",
Move etherscan link logic into module
7 years ago
"etherscan-link": "^1.0.2",
fix(package): update ethjs to version 0.4.0
7 years ago
"ethjs": "^0.4.0",
npm 6 fresh lock + node 8 (#4675) * run npm install with npm 6 and node 8 * npm audit fix --force * bump node version on circleci docker img * bump lodash
6 years ago
"ethjs-contract": "^0.2.3",
Throw if ENS Resolver isn't set up Instead of resolving to name owners, which can encourage inconsistent usage of ENS. Fixes #1427.
8 years ago
"ethjs-ens": "^2.0.0",
deps - bump ethjs-query to fix unhandled promise rejections
7 years ago
"ethjs-query": "^0.3.4",
Move inpage-provider and port-stream outside With the creation of the [metamask-extension-provider](https://github.com/MetaMask/metamask-extension-provider) we have our first non-core module that is dependent on the inpage-provider and port-stream. To reduce the size of its dependencies, I have moved the [metamask-inpage-provider](https://github.com/MetaMask/metamask-inpage-provider) into its own module, as well as [extension-port-stream](https://github.com/MetaMask/extension-port-stream). This allows them to be more easily depended & iterated on by external projects.
6 years ago
"extension-port-stream": "^1.0.0",
bump extensionizer version to 1.0.1 (see https://github.com/MetaMask/extensionizer/pull/4)
7 years ago
"extensionizer": "^1.0.1",
introduce tx-state-history-helper and diff-based history
7 years ago
"fast-json-patch": "^2.0.4",
toggle wired up to preferences property store
7 years ago
"fuse.js": "^3.2.0",
address book entries by chainId (#7205)
5 years ago
"gaba": "^1.7.0",
Bump human-standard-token-abi version for DAI support
6 years ago
"human-standard-token-abi": "^2.0.0",
Add latest jazzicon version
8 years ago
"jazzicon": "^1.2.0",
update json-rpc-engine
5 years ago
"json-rpc-engine": "^5.1.4",
npm audit fix
6 years ago
"json-rpc-middleware-stream": "^2.1.1",
Implement latest EIP-712 protocol
6 years ago
"jsonschema": "^1.2.4",
Shuffle tokens
7 years ago
"lodash.debounce": "^4.0.8",
"lodash.shuffle": "^4.2.0",
Add debug logging to ui routing logic.
8 years ago
"loglevel": "^1.4.1",
Fix displayed time and date in the activity log. Remove vreme library, add luxon library. (#5932)
6 years ago
"luxon": "^1.8.2",
Replace `undefined` selectedAddress with `null` (#7161) * Replace `undefined` selectedAddress with `null` The `runtime.Port.postMessage` API will drop keys with a value of `undefined` on Chrome, but not on Firefox. This was a problem for the `publicConfig` stream, which passed the key `selectedAddress` with the value of `undefined` to communicate to dapps that the user had logged out. Instead a `null` is now passed for `selectedAddress` upon logout, which is correctly sent by the `runtime.Port.postMessage` API on both Chrome and Firefox. closes #7101 closes #7109 * Update `metamask-inpage-provider` to v3.0.0 The v3.0.0 update includes a change to the `accountsChanged` event. The event will now emit an empty array instead of an array with `undefined` or `null`. The previous behavior was to emit `[undefined]`. The previous commit would have changed that to `[null]` anyway, so we figured if we're going to make a public-facing change to the event anyway we should change it to be correct. `[undefined]` was never intended, and it technically violates EIP-1193, which states that the `accountsChanged` event should emit an array of strings.
5 years ago
"metamask-inpage-provider": "^3.0.0",
Improve fox logo performance By including metamask-logo@2.1.4 Fixes #3621
7 years ago
"metamask-logo": "^2.1.4",
gulp - add disc bundle analysis task
8 years ago
"mkdirp": "^0.5.1",
working without permission issues
6 years ago
"multihashes": "^0.4.12",
transactions/deps - use broken out nonce-tracker module (#6555)
6 years ago
"nonce-tracker": "^1.0.0",
Tolerate nonces of any format
8 years ago
"number-to-bn": "^1.7.0",
streams - use pump and published obj-multiplex
7 years ago
"obj-multiplex": "^1.0.0",
Remove Babel 6 from internal dependencies (#7037) remove babel@6 from internal deps update internal deps to latest published versions
5 years ago
"obs-store": "^4.0.3",
Derive gas price estimate from previous transactions Return the 50th percentile lowest gas price of the previous 20 blocks.
7 years ago
"percentile": "^1.2.0",
deps - bump ethjs-query to fix unhandled promise rejections
7 years ago
"pify": "^3.0.0",
Fix plugin tests
9 years ago
"polyfill-crypto.getrandomvalues": "^1.0.0",
chore(package): update dependencies
7 years ago
"post-message-stream": "^3.0.0",
Flattened addTx async methods
8 years ago
"promise-filter": "^1.1.0",
Fix issue where generating a new account would put it in loose keys
8 years ago
"promise-to-callback": "^1.0.0",
Fix merge conflicts
7 years ago
"prop-types": "^15.6.1",
Update mobile sync (#6967) * update mobile sync * update lockfile
5 years ago
"pubnub": "4.24.4",
deps - bump pump
7 years ago
"pump": "^3.0.0",
Feature Flag + Mobile Sync (#5955)
6 years ago
"qrcode-generator": "1.4.1",
Reapply conversion utility changes and fix calls to utility in pending-tx.
7 years ago
"ramda": "^0.24.1",
Update greenkeeper deps for master
7 years ago
"react": "^15.6.2",
Allow dragging seed phrase during Confirm Seed Phrase (#6557) * Add basic drag and drop functionality * Refactor seed phrase data structure * Insert to list when drop * Save before refactor * Finish DND * Fix linter * update package-lock.json * Address styling feedbacks * Add box shadow on hover * Finish adding unit tests * Remove describe.only
6 years ago
"react-dnd": "^3.0.2",
"react-dnd-html5-backend": "^7.4.4",
Update greenkeeper deps for master
7 years ago
"react-dom": "^15.6.2",
chore(package): update dependencies
7 years ago
"react-hyperscript": "^3.0.0",
Auto logout after specific time (#6558) * Add i18n strings * Finish Auto timeout * Fix linter * Fix copies * Add unit test to Advanced Tab component * Add back actions and container * Add basic test to ensure container completeness * No zero, fix linters * restrict negative in input
6 years ago
"react-idle-timer": "^4.2.5",
Implement latest EIP-712 protocol
6 years ago
"react-inspector": "^2.3.0",
Add react-media package to prevent rendering wallet-view twice in the popup view
6 years ago
"react-media": "^1.8.0",
chore(package): update dependencies
7 years ago
"react-redux": "^5.0.5",
Add react-router to allow use of the browser back button
7 years ago
"react-router-dom": "^4.2.2",
incremental commit
7 years ago
"react-select": "^1.0.0",
fix(package): update react-simple-file-input to version 2.0.0
7 years ago
"react-simple-file-input": "^2.0.0",
[NewUI] Use tooltip for copy to clipboard helper text on main screen. (#3120) * Use tooltip for display of helper text in wallet views copy to clipboard feature. * Use react-tippy in wallet-view.js; center arrow tooltip throughout tooltip text change. * Remove unnecessary tabIndex attribute from wallet view address element.
7 years ago
"react-tippy": "^1.2.2",
toggle wired up to preferences property store
7 years ago
"react-toggle-button": "^2.2.0",
Add tooltip to copy button
9 years ago
"react-tooltip-component": "^0.3.0",
Replace react-addons-css-transition-group (#6816) This package is deprecated, and is incompatible with React v16. It has been replaced by `react-test-renderer`, which has a drop-in replacement for `react-addons-css-transition-group`. Strangely, `react-test-renderer` was already listed as a dependency despite not being used. I had to downgrade it, as the version already listed was for React v16, and we're still using React v15.
5 years ago
"react-transition-group": "^1.2.1",
Add Integration Tests
7 years ago
"react-trigger-change": "^1.0.2",
incremental commit
7 years ago
"reactify": "^1.1.1",
streams - use pump and published obj-multiplex
7 years ago
"readable-stream": "^2.3.3",
Add UniqueImageScreen
7 years ago
"recompose": "^0.25.0",
Move UI deps into main plugin package.json Also move UI test scripts into main plugin Also move testing explanation to main plugin README.
9 years ago
"redux": "^3.0.5",
chore(package): update dependencies
7 years ago
"redux-logger": "^3.0.6",
"redux-thunk": "^2.2.0",
Patch security update
7 years ago
"request-promise": "^4.2.1",
Refactor and redesign confirm transaction views
7 years ago
"reselect": "^3.0.1",
Tx controller now uses safe event emitter (#5769) * transactions - use safe-event-emitter over events * tests - pass a platform object on init with a noop showTransactionNotification * test - fix for tx-state-history-helper trying to reduce an empty array * deps - safe-event-emitter * lint
6 years ago
"safe-event-emitter": "^1.0.1",
fix asset detection (#6049)
6 years ago
"single-call-balance-checker-abi": "^1.0.0",
Remove unused locale messages (#7190) * Switch to using string literals for locale keys Various message keys were being specified with a string template instead of a string literal. They have been switched to use string literals so that the script for detecting unused messages can find them. * Remove unused locale messages A number of unused locale messages have been removed - probably leftover from old UI elements that have since been removed. The `verify_locale_strings` script has been augmented to search the UI for string literals, and match those against the locale message keys in the `en` locale. Any messages without a corresponding string literal are assumed to be unused. The script has also been updated with an optional `--fix` parameter, which will automatically delete any unused messages from locales. 148 unused messages were found in this case, out of a total of about 650 messages. Another 70 messages are _potentially_ unused and require further investigation, but weren't as easy to rule out because they were found in string literals. * Remove additional unused locale messages The following messages were more difficult to rule out because they were present as string literals in the UI. They do appear to be unused as locale keys though.
5 years ago
"string.prototype.matchall": "^3.0.1",
bugfix - prevents old blocktracker from getting internal hooks migrated
6 years ago
"swappable-obj-proxy": "^1.1.0",
Move UI deps into main plugin package.json Also move UI test scripts into main plugin Also move testing explanation to main plugin README.
9 years ago
"textarea-caret": "^3.0.1",
Validate URIs before entering them in.
8 years ago
"valid-url": "^1.0.9",
npm audit fix
6 years ago
"web3": "^0.20.7",
Remove Babel 6 from internal dependencies (#7037) remove babel@6 from internal deps update internal deps to latest published versions
5 years ago
"web3-stream-provider": "^4.0.0",
added webrtc-adapter for browser compat
6 years ago
"webrtc-adapter": "^6.3.0",
working without permission issues
6 years ago
"xtend": "^4.0.1"
init commit
9 years ago
},
"devDependencies": {
Upgrade to Babel 7 (#6942) Babel 7 moved to a new configuration format, and they've scoped all of their packages under `@babel/`. This brings MetaMask in-line with dependencies we use that _already_ use Babel 7, and it eliminates a few unfortunate edge cases that can prevent dependencies from being correctly transpiled.
5 years ago
"@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 - npm scripts for uploading source maps
7 years ago
"@sentry/cli": "^1.30.3",
Break Storybook-related pkgs to reduce listed vulnerabilities
6 years ago
"@storybook/addon-info": "^5.1.1",
Merge branch 'develop' into i3725-refactor-send-component-
7 years ago
"@storybook/addon-knobs": "^3.4.2",
Break Storybook-related pkgs to reduce listed vulnerabilities
6 years ago
"@storybook/react": "^5.1.1",
updated ganache and addons-linter (#7204)
5 years ago
"addons-linter": "1.14.0",
Upgrade to Babel 7 (#6942) Babel 7 moved to a new configuration format, and they've scoped all of their packages under `@babel/`. This brings MetaMask in-line with dependencies we use that _already_ use Babel 7, and it eliminates a few unfortunate edge cases that can prevent dependencies from being correctly transpiled.
5 years ago
"babel-eslint": "^10.0.2",
"babelify": "^10.0.0",
npm 6 fresh lock + node 8 (#4675) * run npm install with npm 6 and node 8 * npm audit fix --force * bump node version on circleci docker img * bump lodash
6 years ago
"brfs": "^1.6.1",
npm audit fix
6 years ago
"browserify": "^16.2.3",
ci - build-artifacts - generate sesify-viz for inspecting deps (#7151) * ci - build-artifacts - generate sesify-viz for inspecting deps * lint fix
5 years ago
"browserify-transform-tools": "^1.7.0",
chore(package): update dependencies
7 years ago
"chai": "^4.1.0",
Update chromedriver pkg
6 years ago
"chromedriver": "^2.41.0",
Replace deprecated shell-parallel with concurrently (#6807) * Replace shell-parallel with concurrently * Update ganache-cli
5 years ago
"concurrently": "^4.1.1",
chore(package): update coveralls to version 3.0.0
7 years ago
"coveralls": "^3.0.0",
use 'cross-env' for env-variables within npm scripts, re #3426
7 years ago
"cross-env": "^5.1.4",
Break Storybook-related pkgs to reduce listed vulnerabilities
6 years ago
"css-loader": "^2.1.1",
Move UI deps into main plugin package.json Also move UI test scripts into main plugin Also move testing explanation to main plugin README.
9 years ago
"deep-freeze-strict": "^1.1.1",
chore(package): update dependencies
7 years ago
"del": "^3.0.0",
ci - install deps - limit install scripts to whitelist (#7208) * ci - install deps - limit install scripts to those needed for build * Update .circleci/scripts/deps-install.sh Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * ci - install deps - expand install scripts needed for tests * ci - install deps - expand install scripts needed for integration tests * ci - install deps - fix node-sass script ref * github - set codeowners for scripts/deps-install * development - add utility to show deps with install scripts * lint fix * deps - move read-installed to devDeps
5 years ago
"read-installed": "^4.0.3",
ci - build-artifacts - generate sesify-viz for inspecting deps (#7151) * ci - build-artifacts - generate sesify-viz for inspecting deps * lint fix
5 years ago
"deps-dump": "^1.1.0",
build - add envify to bundle process
8 years ago
"envify": "^4.0.0",
chore(package): update enzyme to version 3.4.4
6 years ago
"enzyme": "^3.4.4",
chore(package): update enzyme-adapter-react-15 to version 1.0.6
6 years ago
"enzyme-adapter-react-15": "^1.0.6",
Add eslint dependency (#6842) We had forgotten to add `eslint` as a dependency, even though we use it directly. It had always worked because we have dependencies that also depend upon it. `eslint` has also been updated to v6, which necessitated two minor changes.
5 years ago
"eslint": "^6.0.1",
Add Mocha/Chai eslint plugins
8 years ago
"eslint-plugin-chai": "0.0.1",
lint - lint json files in app/
7 years ago
"eslint-plugin-json": "^1.2.0",
chore(package): update eslint-plugin-mocha to version 5.0.0
7 years ago
"eslint-plugin-mocha": "^5.0.0",
More lint fixes
7 years ago
"eslint-plugin-react": "^7.4.0",
test - add actions unit tests (#5369) * Actions.spec.js * Error handling tests * Lint
6 years ago
"fetch-mock": "^6.5.2",
Merge branch 'develop' into i3725-refactor-send-component-
7 years ago
"file-loader": "^1.1.11",
fix merge conflicts
6 years ago
"fs-extra": "^6.0.1",
deps - bump watchify
7 years ago
"fs-promise": "^2.0.3",
Replace deprecated shell-parallel with concurrently (#6807) * Replace shell-parallel with concurrently * Update ganache-cli
5 years ago
"ganache-cli": "^6.4.4",
updated ganache and addons-linter (#7204)
5 years ago
"ganache-core": "2.8.0",
npm audit fix
6 years ago
"geckodriver": "^1.16.2",
npm 6 fresh lock + node 8 (#4675) * run npm install with npm 6 and node 8 * npm audit fix --force * bump node version on circleci docker img * bump lodash
6 years ago
"gh-pages": "^1.2.0",
Deduplicate package.json file From `npm install`: > npm WARN The package css-loader is included as both a dev and production dependency. > npm WARN The package eslint-plugin-react is included as both a dev and production dependency. > npm WARN The package file-loader is included as both a dev and production dependency. > npm WARN The package gulp is included as both a dev and production dependency. It's also worth noting that the Gulp version we were using was inconsistent and there is a published v4 release on GitHub.
6 years ago
"gulp": "^4.0.0",
"gulp-autoprefixer": "^5.0.0",
[NewUI] Build mascara with uglification and gzipping. (#2735) * Adds uglification and gzipping. * Build mascara with uglification and gzipping. * Remove gzipping from extension build.
7 years ago
"gulp-babel": "^7.0.0",
Deduplicate package.json file From `npm install`: > npm WARN The package css-loader is included as both a dev and production dependency. > npm WARN The package eslint-plugin-react is included as both a dev and production dependency. > npm WARN The package file-loader is included as both a dev and production dependency. > npm WARN The package gulp is included as both a dev and production dependency. It's also worth noting that the Gulp version we were using was inconsistent and there is a published v4 release on GitHub.
6 years ago
"gulp-debug": "^3.2.0",
"gulp-eslint": "^4.0.0",
Performance: Delivery optimized images (#7176)
5 years ago
"gulp-imagemin": "^6.1.0",
Add platform specific builds and zip tasks (#486) * Add platform specific folders to dist folder * Remove gulp hacks * Add platform specific bundling dev and dist tasks now build into platform-specific folders within the `dist` folder. Added tasks `gulp zip` and `gulp dist`. `zip` builds the platform-specific folders into platform-specific bundles within the `dist` folder. `dist` builds and then zips all at once. * Fix chrome bundle zipping * Fix broken reference in eth warning * Fix but where web3.eth.accounts are not available in firefox. * Bump changelog
8 years ago
"gulp-json-editor": "^2.2.1",
Pin two module versions to avoid flatmap-stream hack (#5839) The flatmap-stream module was compromised. MetaMask was NOT affected, but two of our dependencies could include it if they updated, so I am temporarily pinning those versions until they can be updated consciously. Related to https://github.com/dominictarr/event-stream/issues/116
6 years ago
"gulp-livereload": "4.0.0",
build - use uglifyify and gulp-multi-process for better performance
7 years ago
"gulp-multi-process": "^1.3.1",
Right-to-left CSS (using module for conversion) (#7072) * Create RTL stylesheets using `gulp-rtl` * Handle RTL stylesheet special cases Certain blocks of Sass were set to bypass "rtlcss" using ignore comments. Certain icons had to be flipped 180 degrees. * Switch stylesheets when locale changes A second stylesheet has been added to each HTML page for use with right-to-left locales. It is disabled by default. It is enabled on startup if a RTL locale is set, and when switching to a RTL locale. Similarly the LTR stylesheet is disabled when a RTL locale is used. Unfortunately there is an unpleasant flash of unstyled content when switching between a LTR and a RTL locale. There is also a slightly longer page load time when using a RTL locale (<1s difference). We couldn't think of an easy way to avoid these problems. * Set `dir="auto"` as default on `TextFields`
5 years ago
"gulp-rename": "^1.4.0",
chore(package): update dependencies
7 years ago
"gulp-replace": "^0.6.1",
Right-to-left CSS (using module for conversion) (#7072) * Create RTL stylesheets using `gulp-rtl` * Handle RTL stylesheet special cases Certain blocks of Sass were set to bypass "rtlcss" using ignore comments. Certain icons had to be flipped 180 degrees. * Switch stylesheets when locale changes A second stylesheet has been added to each HTML page for use with right-to-left locales. It is disabled by default. It is enabled on startup if a RTL locale is set, and when switching to a RTL locale. Similarly the LTR stylesheet is disabled when a RTL locale is used. Unfortunately there is an unpleasant flash of unstyled content when switching between a LTR and a RTL locale. There is also a slightly longer page load time when using a RTL locale (<1s difference). We couldn't think of an easy way to avoid these problems. * Set `dir="auto"` as default on `TextFields`
5 years ago
"gulp-rtlcss": "^1.4.0",
Deduplicate package.json file From `npm install`: > npm WARN The package css-loader is included as both a dev and production dependency. > npm WARN The package eslint-plugin-react is included as both a dev and production dependency. > npm WARN The package file-loader is included as both a dev and production dependency. > npm WARN The package gulp is included as both a dev and production dependency. It's also worth noting that the Gulp version we were using was inconsistent and there is a published v4 release on GitHub.
6 years ago
"gulp-sass": "^4.0.0",
chore(package): update dependencies
7 years ago
"gulp-sourcemaps": "^2.6.0",
chore(package): update gulp-stylelint to version 7.0.0
7 years ago
"gulp-stylelint": "^7.0.0",
deps - move gulp-terser-js to devDeps
5 years ago
"gulp-terser-js": "^5.0.0",
deps - add gulp deps
9 years ago
"gulp-util": "^3.0.7",
npm audit fix
6 years ago
"gulp-watch": "^5.0.1",
chore(package): update dependencies
7 years ago
"gulp-zip": "^4.0.0",
Use locally served dapp to test contract calls in e2e beta tests
7 years ago
"http-server": "^0.11.1",
tests - add fetch polyfill
8 years ago
"isomorphic-fetch": "^2.2.1",
npm audit fix
6 years ago
"jsdoc": "^3.6.2",
E2E testing with selenium
7 years ago
"jsdom": "^11.2.0",
chore(package): update dependencies
7 years ago
"jsdom-global": "^3.0.2",
npm audit: Break karma, 1 less low, 1 less high
6 years ago
"karma": "^4.1.0",
test - integration - drop testem for karma
7 years ago
"karma-chrome-launcher": "^2.2.0",
"karma-cli": "^1.0.1",
"karma-firefox-launcher": "^1.0.1",
"karma-qunit": "^1.2.1",
deps - add gulp deps
9 years ago
"lodash.assign": "^4.0.6",
chore(package): update mocha to version 5.0.0
7 years ago
"mocha": "^5.0.0",
chore(package): update dependencies
7 years ago
"mocha-eslint": "^4.0.0",
Move UI deps into main plugin package.json Also move UI test scripts into main plugin Also move testing explanation to main plugin README.
9 years ago
"mocha-jsdom": "^1.1.0",
chore(package): update dependencies
7 years ago
"mocha-sinon": "^2.0.0",
"nock": "^9.0.14",
npm audit fix
6 years ago
"node-sass": "^4.12.0",
npm 6 fresh lock + node 8 (#4675) * run npm install with npm 6 and node 8 * npm audit fix --force * bump node version on circleci docker img * bump lodash
6 years ago
"nyc": "^13.0.0",
Merge branch 'develop' into i3725-refactor-send-component-
7 years ago
"path": "^0.12.7",
fix merge conflicts
6 years ago
"prepend-file": "^1.3.1",
Unit tests for containers, utils and selectors in send_/
7 years ago
"proxyquire": "2.0.1",
First simple version of ui mocker
9 years ago
"qs": "^6.2.0",
Update greenkeeper deps for master
7 years ago
"qunitjs": "^2.4.1",
Add JSDocs Page and Script Includes new script `npm run doc` for generating docs page.
7 years ago
"radgrad-jsdoc-template": "^1.1.3",
Add React and Redux DevTools (#6793) * Add React and Redux DevTools * Conditionally load react-devtools * Add start:dev npm script to run the app with devtools Co-Authored-By: Mark Stacey <markjstacey@gmail.com>
5 years ago
"react-devtools": "^3.6.1",
Update greenkeeper deps for master
7 years ago
"react-test-renderer": "^15.6.2",
Fix existing unit tests
6 years ago
"redux-mock-store": "^1.5.3",
Add enzyme, redux-test-utils, and enzyme-adapter-react-15 to deps
7 years ago
"redux-test-utils": "^0.2.2",
Add React and Redux DevTools (#6793) * Add React and Redux DevTools * Conditionally load react-devtools * Add start:dev npm script to run the app with devtools Co-Authored-By: Mark Stacey <markjstacey@gmail.com>
5 years ago
"remote-redux-devtools": "^0.5.16",
"remotedev-server": "^0.3.1",
Merge branch 'develop' into i3725-refactor-send-component-
7 years ago
"resolve-url-loader": "^2.3.0",
development - create selenium screen shotter
7 years ago
"rimraf": "^2.6.2",
Merge branch 'develop' into i3725-refactor-send-component-
7 years ago
"sass-loader": "^7.0.1",
deps - update package-lock
7 years ago
"selenium-webdriver": "^3.5.0",
ci - build-artifacts - generate sesify-viz for inspecting deps (#7151) * ci - build-artifacts - generate sesify-viz for inspecting deps * lint fix
5 years ago
"sesify": "^4.2.1",
sesify-viz - bump dep for visualization enhancement (#7175) * deps - bump sesify-viz for visualization enhancement * deps - bump sesify-viz for visualization enhancement * deps - bump sesify-viz for visualization enhancement * deps - sesify-viz - use carrot version range Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * deps - update yarn lockfile
5 years ago
"sesify-viz": "^3.0.5",
chore(package): update sinon to version 5.0.0
7 years ago
"sinon": "^5.0.0",
Merge branch 'develop' into i3725-refactor-send-component-
7 years ago
"source-map": "^0.7.2",
ci - create source-map-explorer build-artifacts (#7141) * ci - create source-map-explorer build-artifacts * ci - add source-map-explorer builds to metamaskbot comment * lint fix * ci - source-map-explorer - include all bundles
5 years ago
"source-map-explorer": "^2.0.1",
Add static-server devDependency
6 years ago
"static-server": "^2.2.1",
Merge branch 'develop' into i3725-refactor-send-component-
7 years ago
"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.
5 years ago
"stylelint": "^9.10.1",
chore(package): update stylelint-config-standard to version 18.2.0
7 years ago
"stylelint-config-standard": "^18.2.0",
Run all UI tests
9 years ago
"tape": "^4.5.1",
npm audit fix
6 years ago
"testem": "^2.16.0",
setupUntrustedCommunication and setupTrustedCommunication
7 years ago
"through2": "^2.0.3",
Update vinyl-buffer to version 1.0.1
7 years ago
"vinyl-buffer": "^1.0.1",
chore(package): update vinyl-source-stream to version 2.0.0
7 years ago
"vinyl-source-stream": "^2.0.0",
npm audit fix
6 years ago
"watchify": "^3.11.1"
init commit
9 years ago
},
"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.
5 years ago
"node": "^10.16.0",
"yarn": "^1.16.0"
init commit
9 years ago
}
}