YAML Formatter / Validator / JSON Converter
What "lossy" means here
YAML can express things JSON can't: comments, anchors/aliases (shared structure — the same object referenced twice), merge keys, and explicit type tags. Converting to JSON has to flatten all of that into plain, independent values, so a warning is shown listing exactly which of those a given document used. Converting a truly circular YAML structure (an alias pointing back to one of its own ancestors) is refused outright with an explanation, rather than attempted — JSON has no way to represent it at all. Documents that would expand to an enormous number of elements once every alias is flattened out (a "billion laughs"-style anchor bomb) are refused the same way, before any attempt to build the output — this is checked separately from the size of what you typed, since a tiny document can still expand to hundreds of millions of nodes through nested aliases.