Without this browserify will complain that it can't find all pieces of
gun.js, because it parses the AST for instances of 'require' and doesn't
realize that require has been redefined and they are already present.
Older versions of npm don't support the caret version selector, which
seems to be failing Travis-CI gun build 649.1 & 649.2.
I've switched it to a more backwards-compatible version selector.
Sadly, I can't test if it works on my machine, since the node install
seems to fail on all versions prior to v4. Travis will just need to tell
us :)
Move E2E panic tests into their own dedicated folder so mocha won't
automatically attempt to run it. New npm script (`npm run e2e`) runs
those tests with mocha explicitly.
This solves a number of problems:
- Travis-CI can't run the panic tests without a selenium server, which
requires a ton more setup that simply hasn't been done yet.
- Selenium-webdriver doesn't support node < v4, and immediately fails
the build on those environments.
If at any point in the future we want those tests to run automatically,
here's what we'll need:
- Browserstack or SauceLabs tunneling and auth env variables.
- Bash script to detect node version and only install deps and run the
tests if the environment supports it.
Also, a number of tests had `.only` in front, preventing all the others
from running. They've been removed.
Incorporated the unbuild step into the prepublish lifecycle workflow
Assured that /src files from Unbuild will never be comitted accidentally
Updated the uglify-js depencency and prepublish script for module rename
