Enable installation from npm

[pinheadmz]

This is the branch I'm using to test the easy-installer script.

Closes #173

• [x] Make all dependencies required to run the app install by default
• [x] Fix webpack aliases since node_modules is installed in different places by git vs npm
• [x] Ensure plugin installation is to same node_modules dir as bpanel's dependencies
• [ ] Check for other possible node_modules problems - caching in webpack.config.js or testing in karma.conf.js?
• [ ] Check for dependencies that don't need to install, put them back in devDependencies

To test:

GIT

git clone https://github.com/pinheadmz/bpanel
cd bpanel
git checkout npmidev
npm install
npm run start:poll

NPM

option 1:

npm install pinheadmz/bpanel#npmidev
cd node_modules/@bpanel/bpanel
npm run start:poll

option 2 (ensure no weird relative paths from cwd):

npm install pinheadmz/bpanel#npmidev
node --max_old_space_size=4096 node_modules/@bpanel/bpanel/server/index.js --dev --watch-poll

• [ ] Make sure the app runs
• [ ] Make sure modules are all installed in the right place with no redundancies

[bucko13]

I wonder if we can get around having to do that long node command by adding a bin similar to the way bcoin works for example (or even w/ webpack, you can see it has a much simpler command to run from command line ./node_modules/.bin/webpack

[pinheadmz]

You mean the command to start bpanel?

[bucko13]

Yep, instead of node --max_old_space_size=4096 node_modules/@bpanel/bpanel/server/index.js --dev --watch-poll. if we have a ./bin/bpanel it could consolidate all of that.

[bucko13]

and if running from an npm script, if we had the bin, you could just do something like:

"bpanel": "bpanel [...args for bpanel]"

in your package.json scripts object, or even run from command line if installed globally.