Default output formatting conflicts with yamllint

[lucasgonze]

1. Generate an object
2. Output yaml using js-yaml
3. Feed the output into yamllint
4. There will be collisions with default rules:

• "too few spaces before comment" (1 space before comment at end of line instead of 2)
• padding square brackets with spaces
• in one case a whitespace line with nothing but 10 spaces

This issue is flowing from one in mheap/pin-github-action#74, which itself flowed out of an issue in the magma/magma repo.

[rlidwka]

I think we would have the same answer as yaml:
eemeli/yaml#398 (comment)

This library is primarily a parser. We don't provide many formatting options, because that's a bottomless pit of feature requests for every single style choice out there.

Thus, I'd recommend using a dedicated yaml formatter if formatting matters for you.