structure: strict order of json manifests

[quadrophobiac]

The current order of the respective package.json files has created duplication of bower_components and node_modules.

To resolve this for future versions I suggest creating an additional root package.json that handles node dependencies and deprecating node dependencies listed in app/package.json (node require within app/ will resolve to searching parent directory) and leaving app/package.json responsible for stipulating the electron main process.

Bower.json can remain within app/ for now as the complete modularisation of javascript requirements is still pending (there are lots of script tags that need refactoring)

app/package.json

{
  "name": "comma-chameleon",
  "version": "0.1.0",
  "main": "main.js"
}

/package.json

{
  "name": "comma-chameleon",
  "version": "0.1.0",
  "license": "MIT",
  "main": "main.js",
  "scripts": {
    "start": "electron app"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/theodi/comma-chameleon.git"
  },
  "dependencies": {
    "request": "^2.60.0",
    "xlsx": "^0.8.0",
    "node-zip": "^1.1.1"
  },
  "devDependencies": {
    "chai": "^3.2.0",
    "electron-mocha": "^0.3.1",
    "electron-prebuilt": "^0.33.0"
  }
}

[quadrophobiac]

suggestions made here are all covered by any future move to yarn (see #158) so I am closing this ticket for now