Wolf
New Options
Today the only available option is `log` to provide a custom logging function. It's a good escape hatch that's highly flexible, but I'm wondering if there should be other options...
* Development/production bundle location for `es-react` was swapped * Fixed most React warnings: * Incorrect prop names * Array of root nodes instead of `React.Fragment` was warning about needing keys
Not sure if you're interested in supporting this use case, but I think it would be cool to have a [Service Worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) that would allow for viewing and modifying gists...
It looks like one of the goals of this project is to reduce the bloat needed for a web-based code editor. I ran a quick coverage profile and found that...
On the one hand - this project still feels too new to give it the 1.0 seal of approval. On the other hand - there have been very few (minor)...
I'm thinking maybe we could introduce a three element array test expectation where the first string is a modifier string for tests that want to use this feature: ```js export...
This would give the same reduced output as watch mode prints. The default should remain to show the verbose output. Possible overlap with #11. Possible names: - `--min` - `--minimum`...
Should this be only for the entire test file export or also for groupings of tests?
Customize the test results output. In pieces and/or by a user-provided `formatTests` function.
Very low priority. The focus of this project is keeping things simple.