js-yaml
5.5.0 · 15 Oct 2026MIT322.7M / weekRepositoryHomepagenpmAtom feed
Upgrading js-yaml from 5.2.3 to 5.3.0
1 release in betweenevery note read
- 2
- changes to make
- 0
- advisories fixed
- 3
- new
- 2
- fixes
Before you upgrade
Tick each one off as you go- breaking5.3.0
- deprecated5.3.0
Security
1 advisory still affects 5.3.0
- js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sourcesmoderate · GHSA-r3ph-w7gj-g6xm
Upgrading to 5.4.1 clears it.
Release by release
- new
Added completely new documentation.
- new
Exported
DUMP_SCHEMA, the default schema used by the dumper. - new
Added
YAMLException.throwAt()for throwing an error at a source position. - fixed
Validate
<<sequence items at merge time, so aliased merge sources are checked too. - fixed
Resolve
<<outside of a mapping key as the plain string'<<', matching v4, instead of leaking an internal symbol into the result.
- new
2 other lines we could not sort, mostly version bumps
- 5.3.0
Changed flat constant exports to grouped exports:
EVENT_ID,SCALAR_STYLE,COLLECTION_STYLE, andCHOMPING_MODE, along with their value types. The old exports are still preserved, but deprecated. - 5.3.0
Made
identifymandatory for custom tag definitions. Useidentify: () => falsefor load-only tags.