Skip to content

switch from js-yaml to yaml #33

Description

@pi0

Context: Pointed out by @remcohaszing in x npm:yaml is much more spec-compliant than npm:js-yaml

The main reason for choosing js-yaml was that it is ~10x faster and it is important for recurring reads (especially for cases like markdown front matter) but if spec compliant is better I think switch would make sense.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions