Skip to content

fix: correct js-yaml maintenance status in intro. #816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dreyfus92 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: correct js-yaml maintenance status in intro. #816

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/modules/js-yaml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: Modern alternatives to js-yaml for YAML parsing and stringifying

# Replacements for `js-yaml`

`js-yaml` appears to be unmaintained and has known spec-compliance issues.
`js-yaml` is actively maintained. Alternatives below may still be preferable for comment/AST support, zero dependencies, or Bun-native usage.

Comment on lines +7 to 8

@gameroman gameroman Jul 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd just remove this completely

Suggested change
`js-yaml` is actively maintained. Alternatives below may still be preferable for comment/AST support, zero dependencies, or Bun-native usage.

@dreyfus92 dreyfus92 Jul 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair on not asserting maintenance status, it'll just rot and we'll end up back here with another issue. but i'd rather not strip the intro entirely, since a reader landing here with no context reads the alternatives as "migrate now, this is dead." how about we drop the status claim and frame it around what the alternatives give you instead:

"The alternatives below can offer better spec compliance, comment/AST support, zero dependencies, or native Bun support."

keeps it accurate, no claim that ages. wdyt?

@gameroman gameroman Jul 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd just mention "better spec compliance" and "smaller install size"

## `yaml`

Expand Down