Bump devalue from 5.8.1 to 5.9.4

[dependabot]

Bumps devalue from 5.8.1 to 5.9.4.

Release notes

Sourced from devalue's releases.

v5.9.4

Patch Changes

• 067b125: perf: annotate module-level Object.freeze calls as pure so unused operation tables tree-shake

v5.9.3

Patch Changes

• 6861dbb: fix: avoid scanning sparse array holes in uneval traversal and shared-array population
• 9ec5130: fix: reject non-string null-prototype object keys in parse and unflatten to prevent bypassing the __proto__ check
• dae8153: fix: prevent unhandled internal rejections in stringifyAsync when serializing multiple promises
• 84f6f67: fix: prevent quadratic uneval output expansion for repeated strings and bigints
• 6861dbb: fix: avoid eager allocation when evaluating sparse arrays emitted by uneval
• 8f8d78e: fix: validate revived backing buffers before constructing typed arrays
• 46dc877: fix: serialize only the visible bytes of Node Buffers in stringify, stringifyAsync and uneval, preventing disclosure of unrelated data from their shared allocation pool

v5.9.2

Patch Changes

• 8b2a456: fix: reject out-of-bounds indices

v5.9.1

Patch Changes

• 39457ce: fix: uneval emits valid JS for graphs with more than 65534 repeated references
• 686e379: fix: emit valid JS for Node Buffer in uneval
• 376b65c: fix: preserve -0 in float typed arrays in uneval

v5.9.0

Minor Changes

• 07d6a38: feat: export filterArrayIndices, the array-index filtering used by the indicesOf stringify operation, so custom operations can reuse it instead of reimplementing it
• 07d6a38: feat: add pluggable operations option to parse/unflatten, allowing customization of how values are constructed while reviving (e.g. cross-realm or foreign-runtime revival)
• 5b53532: feat: add pluggable operations option to stringify/stringifyAsync, allowing customization of how values are introspected during serialization (e.g. side-effect-free or foreign-runtime serialization)

v5.8.2

Patch Changes

• 48cc81f: fix: serialize DataView subviews with the correct byte offset and length
• cd6da94: fix: resolve circular references through custom revivers when payload is already hydrated
• 29a3382: fix: uneval now produces valid output for a repeated empty Map or Set
• 8c0db06: fix: serialize Temporal values referenced more than once in uneval
• 3770846: fix: emit valid JS for BigInt64Array and BigUint64Array in uneval
• 756265a: fix: preserve shared-reference identity for Map keys in uneval
• faa8a05: fix: emit uneval reconstructions before the statements that reference them
• 06129ad: fix: do not grow sparse arrays by one slot in uneval

Changelog

Sourced from devalue's changelog.

5.9.4

Patch Changes

• 067b125: perf: annotate module-level Object.freeze calls as pure so unused operation tables tree-shake

5.9.3

Patch Changes

• 6861dbb: fix: avoid scanning sparse array holes in uneval traversal and shared-array population
• 9ec5130: fix: reject non-string null-prototype object keys in parse and unflatten to prevent bypassing the __proto__ check
• dae8153: fix: prevent unhandled internal rejections in stringifyAsync when serializing multiple promises
• 84f6f67: fix: prevent quadratic uneval output expansion for repeated strings and bigints
• 6861dbb: fix: avoid eager allocation when evaluating sparse arrays emitted by uneval
• 8f8d78e: fix: validate revived backing buffers before constructing typed arrays
• 46dc877: fix: serialize only the visible bytes of Node Buffers in stringify, stringifyAsync and uneval, preventing disclosure of unrelated data from their shared allocation pool

5.9.2

Patch Changes

• 8b2a456: fix: reject out-of-bounds indices

5.9.1

Patch Changes

• 39457ce: fix: uneval emits valid JS for graphs with more than 65534 repeated references
• 686e379: fix: emit valid JS for Node Buffer in uneval
• 376b65c: fix: preserve -0 in float typed arrays in uneval

5.9.0

Minor Changes

• 07d6a38: feat: export filterArrayIndices, the array-index filtering used by the indicesOf stringify operation, so custom operations can reuse it instead of reimplementing it
• 07d6a38: feat: add pluggable operations option to parse/unflatten, allowing customization of how values are constructed while reviving (e.g. cross-realm or foreign-runtime revival)
• 5b53532: feat: add pluggable operations option to stringify/stringifyAsync, allowing customization of how values are introspected during serialization (e.g. side-effect-free or foreign-runtime serialization)

5.8.2

Patch Changes

• 48cc81f: fix: serialize DataView subviews with the correct byte offset and length
• cd6da94: fix: resolve circular references through custom revivers when payload is already hydrated
• 29a3382: fix: uneval now produces valid output for a repeated empty Map or Set
• 8c0db06: fix: serialize Temporal values referenced more than once in uneval
• 3770846: fix: emit valid JS for BigInt64Array and BigUint64Array in uneval
• 756265a: fix: preserve shared-reference identity for Map keys in uneval
• faa8a05: fix: emit uneval reconstructions before the statements that reference them
• 06129ad: fix: do not grow sparse arrays by one slot in uneval

Commits

• 434358a Version Packages (#202)
• 067b125 perf: annotate module-level Object.freeze calls as pure (#200)
• 53cd3db Version Packages (#201)
• 46dc877 Merge commit from fork
• 84f6f67 Merge commit from fork
• 6861dbb Merge commit from fork
• 8f8d78e Merge commit from fork
• dae8153 Merge commit from fork
• 9ec5130 Merge commit from fork
• 8ade61d chore: fix bench:compare script (#198)
• Additional commits viewable in compare view

[scholarsmate]

@dependabot rebase

[scholarsmate]

+1