`jsr:@std/yaml` vs `jsr:@eemeli/yaml` (aka `npm:yaml`)

[mb21]

I'm wondering whether anybody has looked more into this.

• @std/yaml says it's "ported from js-yaml v3.13.1"

• e18e says "js-yaml appears to be unmaintained and has known spec-compliance issues." They recommend npm:yaml instead, which is also availabe on JSR as @eemeli/yaml

So, should new projects better use @eemeli/yaml? Perhaps @std/yaml should be changed to be a thin wrapper around jsr:@eemeli/yaml? Or am I missing something, does the current code-base have other benefits?

[timreichen]

Std/yaml code has changed a lot over time from the original port, so I am not sure how much comparable it still is except the core parsing algorithm.
I think it would be interesting to test it against @eemeli/yaml to check if the implementation lacks a feature or bug fix and also on a performance level.

[andrewthauer]

@eemeli/yaml supports an API that lets you modify yaml documents and resave them with minimal to no formatting changes (ie preserve whitespace and comments). This is really useful for some use cases.