Basically per the TAP 13 Specification, comment blocks can be intended with any number of white space:
If the test line is immediately followed by an indented block beginning with /^\s+—/ and ending with ^\s+…/ that block will be interpreted as an inline YAML document.
eslint-tap indents with more than 2 spaces and isn't parsed correctly (yaml blocks are missing).
ok 5 test/testBase.js
not ok 6
---
message: Missing semicolon.
severity: error
file: /home/etc...
line: 6
name: semi
...
ok 7 src/routes/api/auth.js
Basically per the TAP 13 Specification, comment blocks can be intended with any number of white space:
eslint-tap indents with more than 2 spaces and isn't parsed correctly (yaml blocks are missing).