Repository navigation
Can't round-trip out-of-range floating point #737
Description
Describe the bug
When parsing a document with an unquoted string that "looks like" a number, the parser will use the float tag, even though the value cannot be represented by the JavaScript number and ends up getting stored a +Inf or -Inf.
To Reproduce
Steps to reproduce the behaviour:
> require("js-yaml").load("gitsha: 61e9540")
{ gitsha: Infinity }Expected behaviour
Like some other YAML loaders (go-yaml comes to mind), an untagged, unquoted value should only be interpreted as a float if it can be safely stored as such in the native type.
Versions (please complete the following information):
- NodeJS 24.12.0
js-yaml: 4.1.1
Additional context
The YAML 1.2 spec is pretty clear:
Some languages (such as Perl) provide only a "number" type that allows for both integer and floating-point values. A YAML [processor] may use such a type for floating-point numbers, as long as they round-trip properly.
Activity
[-]Can't roundtrip out-of-range floating point[/-][+]Can't round-trip out-of-range floating point[/+]fix(float): reject out-of-range values that would parse to Infinity
Jah-yee commentedon May 9, 2026
fix(float): reject out-of-range values that would parse to Infinity
fix(float): reject out-of-range values that would parse to Infinity
Fix out-of-range number resolution, close #737
chore(deps): update dependency js-yaml to v4.2.0 (#92)
chore(deps): update dependency js-yaml to v4.2.0 (#92)
chore(deps): update dependency js-yaml to v4.2.0 (#92)
fix: round-trip integers that stringify in exponential notation (#771)
chore(deps): update dependency js-yaml to v4.3.2 (#184)