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.
156 Commits
2 Branches
1 Tag
200 MiB
Tag: Branch: Tree: 266e3c7ddb
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '266e3c7ddb'
${ noResults }
ciphermask/package.json

58 lines
1.5 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",
major - migrate to blockapps-web3
9 years ago
"public": false,
deps - add metamas-ui, bump provider-engine
9 years ago
"private": true,
migrate to new ui + provider
9 years ago
"scripts": {
Added basic es6 mocha test suite
9 years ago
"start": "gulp dev",
Made configuration migrateable Abstract all configuration data into a singleton called `configManager`, who is responsible for reading and writing to the persisted storage (localStorage, in our case). Uses my new module [pojo-migrator](https://www.npmjs.com/package/pojo-migrator), and wraps it with the `ConfigManager` class, which we can hang any state setting or getting methods we need. By keeping all the persisted state in one place, we can stabilize its outward-facing API, making the interactions increasingly atomic, which will allow us to add features that require restructuring the persisted data in the long term without having to rewrite UI or even `background.js` code. All the restructuring and data-type management is kept in one neat little place. This should make it very easy to add new configuration options like user-configured providers, per-domain vaults, and more! I know this doesn't seem like a big user-facing feature, but we have a big laundry list of features that I think this will really help streamline.
9 years ago
"test": "mocha --require test/helper.js --compilers js:babel-register --recursive",
"watch": "mocha watch --compilers js:babel-register --recursive"
migrate to new ui + provider
9 years ago
},
init commit
9 years ago
"dependencies": {
deps - bump
9 years ago
"async": "^1.5.2",
idmgmt - refactor
9 years ago
"clone": "^1.0.2",
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",
build - add gulp build process
9 years ago
"eth-lightwallet": "^2.2.2",
deps - update deps
9 years ago
"eth-store": "^1.1.0",
build - add gulp build process
9 years ago
"ethereumjs-tx": "^1.0.0",
metamask provider skeleton
9 years ago
"ethereumjs-util": "^1.3.5",
Added xtend to package.json
9 years ago
"faux-jax": "git+https://github.com/kumavis/faux-jax.git#c3648de04804f3895c5b4972750cae5b51ddb103",
notifications - add tx confirm+cancel buttons
9 years ago
"hat": "0.0.3",
migrate to new ui + provider
9 years ago
"inject-css": "^0.1.1",
deps - bump metamask-ui
9 years ago
"metamask-ui": "^1.5.0",
plumbing - pipe web3 to the popup.js
9 years ago
"multiplex": "^6.7.0",
Made configuration migrateable Abstract all configuration data into a singleton called `configManager`, who is responsible for reading and writing to the persisted storage (localStorage, in our case). Uses my new module [pojo-migrator](https://www.npmjs.com/package/pojo-migrator), and wraps it with the `ConfigManager` class, which we can hang any state setting or getting methods we need. By keeping all the persisted state in one place, we can stabilize its outward-facing API, making the interactions increasingly atomic, which will allow us to add features that require restructuring the persisted data in the long term without having to rewrite UI or even `background.js` code. All the restructuring and data-type management is kept in one neat little place. This should make it very easy to add new configuration options like user-configured providers, per-domain vaults, and more! I know this doesn't seem like a big user-facing feature, but we have a big laundry list of features that I think this will really help streamline.
9 years ago
"pojo-migrator": "^2.1.0",
plumbing - fix rpc feedback loop bug
9 years ago
"pumpify": "^1.3.4",
deps - add readable-stream + bump provider-engine
9 years ago
"readable-stream": "^2.0.5",
plumbing - pipe web3 to the popup.js
9 years ago
"through2": "^2.0.1",
migrate to ProviderEngine zero-client
9 years ago
"web3": "^0.15.1",
Revert "Revert "Etherscan provider""
9 years ago
"web3-provider-engine": "^7.2.1",
Added xtend to package.json
9 years ago
"xtend": "^4.0.1"
init commit
9 years ago
},
"devDependencies": {
Added basic es6 mocha test suite
9 years ago
"babel-preset-es2015": "^6.6.0",
"babel-register": "^6.7.2",
deps - add gulp deps
9 years ago
"browserify": "^13.0.0",
"del": "^2.2.0",
build - add gulp build process
9 years ago
"gulp": "github:gulpjs/gulp#4.0",
"gulp-livereload": "^3.8.1",
deps - add gulp deps
9 years ago
"gulp-sourcemaps": "^1.6.0",
"gulp-util": "^3.0.7",
build - add gulp build process
9 years ago
"gulp-watch": "^4.3.5",
Convert to bip44 hdTrees Added initial test just to verify we can recover the accounts we generate in this way. Still need to add compliance test to make sure this interoperates with testrpc's new mnemonic flag.
9 years ago
"jsdom": "^8.1.0",
Made configuration migrateable Abstract all configuration data into a singleton called `configManager`, who is responsible for reading and writing to the persisted storage (localStorage, in our case). Uses my new module [pojo-migrator](https://www.npmjs.com/package/pojo-migrator), and wraps it with the `ConfigManager` class, which we can hang any state setting or getting methods we need. By keeping all the persisted state in one place, we can stabilize its outward-facing API, making the interactions increasingly atomic, which will allow us to add features that require restructuring the persisted data in the long term without having to rewrite UI or even `background.js` code. All the restructuring and data-type management is kept in one neat little place. This should make it very easy to add new configuration options like user-configured providers, per-domain vaults, and more! I know this doesn't seem like a big user-facing feature, but we have a big laundry list of features that I think this will really help streamline.
9 years ago
"jsdom-global": "^1.7.0",
init commit
9 years ago
"jshint-stylish": "~0.1.5",
deps - add gulp deps
9 years ago
"lodash.assign": "^4.0.6",
Convert to bip44 hdTrees Added initial test just to verify we can recover the accounts we generate in this way. Still need to add compliance test to make sure this interoperates with testrpc's new mnemonic flag.
9 years ago
"mocha": "^2.4.5",
Implemented BIP44 compliance test. Also added the hdPath that Christian had told me to our calls to the LightWallet, but this does not seem to have made us generate the same accounts as `testrpc` yet.
9 years ago
"mocha-sinon": "^1.1.5",
"sinon": "^1.17.3",
deps - add gulp deps
9 years ago
"vinyl-buffer": "^1.0.0",
"vinyl-source-stream": "^1.1.0",
"watchify": "^3.7.0"
init commit
9 years ago
},
"engines": {
"node": ">=0.8.0"
}
}