* feat(ospec): Add spacing before report results
...sometimes tested code emits console.log() messages
which then blend in with ospec's report
* feat(ospec): Reword and prettify the report messages
* feat(ospec): Make console.errors more compact, yet more readable
* docs(ospec): Update change-log.md
* fix(ospec): Fix grammar when number of assertions is 1
* feat(ospec): Make "all passed" message bright green
* refactor(ospec): define `cStyle()` helper for browser styling
* feat(ospec): Use en-dashes for the horizontal divider
* feat(ospec): Revert stacktrace coloring, make context bright red
...and add extra newline above each error - for readability
in commandline (node.js) mode
* feat(ospec): Improve the only-test-passed message
"1 assertion passed" --> "The 1 assertion passed"
* docs: Update LOC count
* Allow requires before running tests
This enables requiring modules like `esm` before any test files are loaded.
* Update ospec documentation
Also add documentation for `--require` option
* Update ospec change-log.md
* [opsec] move the change log item to v2.0
* [ospec] tweak the docs
* feat(ospec): CLI support for file-patterns and an --ignore flag
The added dependency is only used by the node.js binary - which normally only ever installed via npm/yarn anyway.
This does not interfer with ospec proper being dependencyless.
* chore(mithril): Add glob dependency needed by the ospec binary
this is only needed while ospec is inlined in the
mithril repo. As soon as ospec is split away into a
standalone npm module, this will not be required anymore.
* refactor(ospec): Use 'match' events instead of callback
Performance should be similar, but the code looks
cleaner and easier to grok.
* Misc tweaks
Getting set up with ospec is deceptively simple, and adding just a bit
more documentation should help new users from falling into the trap of
overthinking the test config. (I know that I ended up down a very
strange rabbit hole when pulling ospec into a project).
This also adjusts the bin definition in the package file so that we can
hopefully just use the `ospec` command instead of a folder ref.
