JavaScript Projects: run browser tests in CI only

[daviddias]

From @mikeal at ipfs/community#338

One thing I've found that makes contributing very difficult to our JavaScript projects is the browser tests. I've never actually been able to successfully run any of our browser tests in any of the JS projects I've contributed to.

I've gotten in the habit of running test:node and then committing and push with--no-verify which is not a great solution.

There's probably a lot that we can do to improve the runability and reliability of the browser tests, like moving to puppeteer, but that's going to take time. In the meantime, I'd like to remove this barrier to contribution by changing the JS project pre-commit and pre-push definitions to run test:node only.

We should make sure that CI is running the browser tests before contributions get merged, but having them run before every commit and push is rather painful.

[daviddias]

JS Team (@alanshaw, @hugomrdias, @achingbrain), is this something you could take on?

[alanshaw]

Pre-commit/push hooks were removed from most PL JS projects in ipfs/aegir#243 in part because of ipfs-inactive/js-ipfs-http-client#794. So this issue has already been resolved as they do run successfully in CI.

If the browser tests are not working for people locally we need an issue created in the repo for the project, or I need a mention in the issue if you create it somewhere else...but that's less ideal as it prevents others working on it or knowing it exists and I'm just going to open an issue in the relevant project for it anyway 🙄

(If an issue already exists and I've missed it somehow then please ignore 😆)