Releases: anko/txm
v8.2.0
New feature: Output is more compact.
When possible and clear, short YAML strings are displayed on the same line as the key (using '
-strings), rather than on the next line (using |
block notation).
Output that contains single-quotes or newlines, or which would make the line it's on exceed 80 characters, will still be displayed with block notation, for clarity.
Before:
program: 'cat'
stderr: ''
input location: |
line 4
output location: |
line 8
error location: |
line 12
program location: |
line 1
After:
program: 'cat'
stderr: ''
input location: 'line 4'
output location: 'line 8'
error location: 'line 12'
program location: 'line 1'
v8.1.0
New feature: Invisible C0 Control Characters are now made visible, if they appear in the addition/removal part of diffs, using the appropriate standard Unicode stand-in symbols. If such replacements are made, the test's output includes an index for easy lookup. This may help clarify situations involving mixed spaces, tabs, newlines, and the like.
See the feature's readme section for more details.
v8.0.0
Big, so I figure I should finally start doing release notes.
Breaking changes
- If you're using this package programmatically, as a
require
d JavaScript module, then you'll have to upgrade to ESMimport
s, because that's how the library is exposed now. See Sindre Sorhus' helpful document if you're feeling unsure how to migrate.
New features
-
New
!test
commands:exit
,only
. See the readme. -
You can finally use
<<
inside HTML comments now, so you can do shell heredocs. Not because upstream fixed their bug, but because I rejected their reality and substituted my own. -
New
TXM_HAS_COLOR
/TXM_HAS_COLOUR
env variable exposed to tests, which you can use to force colour on at appropriate times, if you're using a custom assert library incheck
tests. (Colours you output onstdout
/stderr
show up as part of the error message.) -
Better error messages and documentation improvements.
-
Lighter package; fewer dependencies. Removed yargs, parse5-sax-parser, concat-stream, and wrote the necessary parts myself, because they're not worth the bloat for how little of them we're using. Likely much faster too.
Background maintenance details for nerds
-
I moved the package to ES modules, so the future is here. Was necessary to upgrade dependencies that had moved to ESM. (Tests still use
require
for now. I'll get around eventually to porting them to real JavaScript.) -
I git CI working on Github Actions, in a way that automatically tests against Node Active LTS.