formatting.js attempts to require "chalk" when require is defined as a function. This causes Stacky to throw errors when it's being used in a browser and require.js is present.

When doing 'bower install stacky', the lib folder is missing in the installed directory.
This causes error when running web component tester's test case.

stacky uses this code to detect Node.js.

var isNode = new Function('try {return this===global;}catch(e){return false;}');

However this way of detecting node is completely wrong.

First issue, the practical one. If you use the <script> version of babel-polyfill this code will declare that the browser isNode and stacky will attempt to require things.

Second problem, the idealistic one. Adding global to browsers was a proposal that made it to stage-3, i.e. nearly included into the standard and implementation attempted by browsers.

This kind of irresponsible code that equates global to Node.js/CommonJS/require is the reason we're having an issue with getting that to stage-4.

This change: mochajs/mocha@68ba3b2 tries to toString the error to report the message. Stacky "normalized" errors do not have a toString, so we should provide one.

So you don't have to include all the things