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",
|
2015-10-10 08:14:18 +02:00
|
|
|
"public": false,
|
2016-02-08 20:47:42 +01:00
|
|
|
"private": true,
|
2016-01-15 03:26:54 +01:00
|
|
|
"scripts": {
|
2016-03-25 01:51:46 +01:00
|
|
|
"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.
2016-03-31 04:15:49 +02:00
|
|
|
"test": "mocha --require test/helper.js --compilers js:babel-register --recursive",
|
2016-04-14 00:46:39 +02:00
|
|
|
"watch": "mocha watch --compilers js:babel-register --recursive",
|
|
|
|
|
"testUi": "mocha ui/test/**/*test.js",
|
|
|
|
|
"watchUi": "mocha watch ui/test/**/*test.js"
|
|
|
|
|
},
|
|
|
|
|
"browserify": {
|
|
|
|
|
"transform": [
|
|
|
|
|
[
|
|
|
|
|
"babelify",
|
|
|
|
|
{
|
|
|
|
|
"presets": [
|
|
|
|
|
"es2015"
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
],
|
|
|
|
|
"brfs"
|
|
|
|
|
]
|
2016-01-15 03:26:54 +01:00
|
|
|
},
|
2015-08-01 03:38:02 +02:00
|
|
|
"dependencies": {
|
2016-02-10 20:47:21 +01:00
|
|
|
"async": "^1.5.2",
|
2016-02-11 02:44:46 +01:00
|
|
|
"clone": "^1.0.2",
|
2016-04-14 00:46:39 +02:00
|
|
|
"copy-to-clipboard": "^2.0.0",
|
|
|
|
|
"debounce": "^1.0.0",
|
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",
|
2016-03-03 08:06:43 +01:00
|
|
|
"eth-lightwallet": "^2.2.2",
|
2016-02-11 03:28:57 +01:00
|
|
|
"eth-store": "^1.1.0",
|
2016-03-03 08:06:43 +01:00
|
|
|
"ethereumjs-tx": "^1.0.0",
|
2016-04-14 23:34:52 +02:00
|
|
|
"ethereumjs-util": "^4.3.0",
|
2016-02-15 11:19:08 +01:00
|
|
|
"faux-jax": "git+https://github.com/kumavis/faux-jax.git#c3648de04804f3895c5b4972750cae5b51ddb103",
|
2016-03-12 02:13:48 +01:00
|
|
|
"hat": "0.0.3",
|
2016-01-15 03:26:54 +01:00
|
|
|
"inject-css": "^0.1.1",
|
2016-04-14 00:46:39 +02:00
|
|
|
"metamask-logo": "^1.1.5",
|
2016-03-10 03:33:30 +01:00
|
|
|
"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.
2016-03-31 04:15:49 +02:00
|
|
|
"pojo-migrator": "^2.1.0",
|
2016-03-10 22:04:45 +01:00
|
|
|
"pumpify": "^1.3.4",
|
2016-04-14 00:46:39 +02:00
|
|
|
"react": "^15.0.1",
|
|
|
|
|
"react-addons-css-transition-group": "^15.0.1",
|
|
|
|
|
"react-dom": "^15.0.1",
|
|
|
|
|
"react-hyperscript": "^2.4.0",
|
2016-02-10 21:04:39 +01:00
|
|
|
"readable-stream": "^2.0.5",
|
2016-04-14 00:46:39 +02:00
|
|
|
"react": "^0.14.3",
|
|
|
|
|
"react-addons-css-transition-group": "^0.14.7",
|
|
|
|
|
"react-dom": "^0.14.3",
|
|
|
|
|
"react-hyperscript": "^2.2.2",
|
|
|
|
|
"react-redux": "^4.0.3",
|
|
|
|
|
"redux": "^3.0.5",
|
|
|
|
|
"redux-logger": "^2.3.1",
|
|
|
|
|
"redux-thunk": "^1.0.2",
|
|
|
|
|
"textarea-caret": "^3.0.1",
|
|
|
|
|
"three.js": "^0.73.2",
|
2016-03-10 03:33:30 +01:00
|
|
|
"through2": "^2.0.1",
|
2015-12-19 07:05:16 +01:00
|
|
|
"web3": "^0.15.1",
|
2016-04-01 01:32:35 +02:00
|
|
|
"web3-provider-engine": "^7.2.1",
|
2016-02-15 11:19:08 +01:00
|
|
|
"xtend": "^4.0.1"
|
2015-08-01 03:38:02 +02:00
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
2016-04-14 00:46:39 +02:00
|
|
|
"brfs": "^1.4.3",
|
2016-03-25 01:51:46 +01:00
|
|
|
"babel-preset-es2015": "^6.6.0",
|
2016-04-14 00:46:39 +02:00
|
|
|
"babelify": "^7.2.0",
|
2016-03-25 01:51:46 +01:00
|
|
|
"babel-register": "^6.7.2",
|
2016-04-14 00:46:39 +02:00
|
|
|
"beefy": "^2.1.5",
|
2016-03-03 08:29:43 +01:00
|
|
|
"browserify": "^13.0.0",
|
2016-04-14 00:46:39 +02:00
|
|
|
"chai": "^3.5.0",
|
|
|
|
|
"deep-freeze-strict": "^1.1.1",
|
2016-03-03 08:29:43 +01:00
|
|
|
"del": "^2.2.0",
|
2016-03-03 08:06:43 +01:00
|
|
|
"gulp": "github:gulpjs/gulp#4.0",
|
|
|
|
|
"gulp-livereload": "^3.8.1",
|
2016-03-03 08:29:43 +01:00
|
|
|
"gulp-sourcemaps": "^1.6.0",
|
|
|
|
|
"gulp-util": "^3.0.7",
|
2016-03-03 08:06:43 +01:00
|
|
|
"gulp-watch": "^4.3.5",
|
2016-03-25 20:41:18 +01:00
|
|
|
"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.
2016-03-31 04:15:49 +02:00
|
|
|
"jsdom-global": "^1.7.0",
|
2015-08-01 03:38:02 +02:00
|
|
|
"jshint-stylish": "~0.1.5",
|
2016-03-03 08:29:43 +01:00
|
|
|
"lodash.assign": "^4.0.6",
|
2016-03-25 20:41:18 +01:00
|
|
|
"mocha": "^2.4.5",
|
2016-04-14 00:46:39 +02:00
|
|
|
"mocha-jsdom": "^1.1.0",
|
2016-03-25 22:51:19 +01:00
|
|
|
"mocha-sinon": "^1.1.5",
|
|
|
|
|
"sinon": "^1.17.3",
|
2016-04-14 00:46:39 +02:00
|
|
|
"uglifyify": "^3.0.1",
|
2016-03-03 08:29:43 +01:00
|
|
|
"vinyl-buffer": "^1.0.0",
|
|
|
|
|
"vinyl-source-stream": "^1.1.0",
|
|
|
|
|
"watchify": "^3.7.0"
|
2015-08-01 03:38:02 +02:00
|
|
|
},
|
|
|
|
|
"engines": {
|
|
|
|
|
"node": ">=0.8.0"
|
|
|
|
|
}
|
|
|
|
|
}
|
