Remove dependency on browserify

[benjamn]

We don't need browserify for anything except running the test suite in a browser, and it pulls in a ton of dependencies that slow down npm install considerably.

[ForbesLindesay]

Why not use devDependencies. These are only installed when you explicitly run npm install in the regenerator directory. This means they don't add bloat to production, but can be safely used in unit tests. At the moment you have a dependency in your tests that isn't specified in package.json

[benjamn]

Do you know if Travis CI runs npm install in the package directory? Speeding up tests was one of the main motivations here.

I'm inclined to wait to add it back until browserify is actually necessary for running tests.

[ForbesLindesay]

travis does, but you shouldn't be having a problem with travis build speed. I can't see how travis taking an extra 10 seconds or so can ever be a serious hindrance to development speed? You do however want to get rid of any dependencies that aren't needed at runtime so people don't have to install them when they just depend on regenerator.

mocha should never be an optionalDependency, since it's pretty much never needed at runtime.

[benjamn]

@ForbesLindesay wanna make a pull request to fix this up?

[ForbesLindesay]

done in #46