Convert config files both ways, with line and column error reporting
The result shows up hereParsed with js-yaml, so anchors, multi-line strings and comments all work. Parse errors report the exact line and column.
Maps, lists and scalars convert cleanly, but comments are dropped and anchors/aliases are expanded to their values — JSON has no equivalent for them.
No. The YAML spec forbids tab indentation — use spaces, conventionally two per level. Check indentation first when parsing fails.