chore(deps): bump safe-stable-stringify from 2.3.1 to 2.5.0

[dependabot]

Bumps safe-stable-stringify from 2.3.1 to 2.5.0.

Release notes

Sourced from safe-stable-stringify's releases.

v2.5.0

• Accept Array#sort(comparator) comparator method as deterministic option value to use that comparator for sorting object keys.

import { configure } from 'safe-stable-stringify'
const object = {
a: 1,
b: 2,
c: 3,
}
const stringify = configure({
deterministic: (a, b) => b.localeCompare(a)
})
stringify(object)
// '{"c": 3,"b":2,"a":1}'

• Very minor performance optimization.

Thanks to @​flobernd, @​cesco69 and @​prisis to contribute to this release!

v2.4.3

• Fixed toJSON function receiving array keys as number instead of string
• Fixed replacer function receiving array keys as number instead of string
• Fixed replacer function not being called for TypedArray entries
• Improved performance to escape long strings that contain characters that need escaping

v2.4.2

• Improved ESM TypeScript types.
• More precise TypeScript replacer type.

v2.4.1

• More precise TypeScript types. The return type is now either string, undefined or string | undefined depending on the input.

v2.4.0

• Added strict option to verify that the passed in objects are fully compatible with JSON without removing information. If not, an error is thrown.
• Fixed TypeScript definition for ESM code bases

Changelog

Sourced from safe-stable-stringify's changelog.

v2.5.0

• Accept Array#sort(comparator) comparator method as deterministic option value to use that comparator for sorting object keys.

import { configure } from 'safe-stable-stringify'
const object = {
a: 1,
b: 2,
c: 3,
}
const stringify = configure({
deterministic: (a, b) => b.localeCompare(a)
})
stringify(object)
// '{"c":3,"b":2,"a":1}'

• Very minor performance optimization.

Thanks to @​flobernd, @​cesco69 and @​prisis to contribute to this release!

v2.4.3

• Fixed toJSON function receiving array keys as number instead of string
• Fixed replacer function receiving array keys as number instead of string
• Fixed replacer function not being called for TypedArray entries
• Improved performance to escape long strings that contain characters that need escaping

v2.4.2

• Improved ESM TypeScript types.
• More precise TypeScript replacer type.

v2.4.1

• More precise TypeScript types. The return type is now either string, undefined or string | undefined depending on the input.

v2.4.0

• Added strict option to verify that the passed in objects are fully compatible with JSON without removing information. If not, an error is thrown.
• Fixed TypeScript definition for ESM code bases

Commits

• a850d28 v2.5.0
• ff9126d doc: update CHANGELOG.md for v2.5.0
• d2e996d refactor: reduce code size and improve performance
• 3e16978 ci: test Node.js v22 instead of v21
• 38afd20 doc: add comparator description
• 9a988d0 feat: accept comparator function as deterministic option (#49)
• 7b7ec1b Update index.js
• 46f2449 bench: fix array creation in benchmark
• 9244319 ci: add Node.js 20.x and 21.x to the tests
• 752b9e9 test: fix test suite for Node.js <= 11
• Additional commits viewable in compare view

[claude]

LGTM — routine minor version bump of a small dependency (safe-stable-stringify 2.3.1 → 2.5.0).

Extended reasoning...

Overview

This PR only touches package.json and package-lock.json, bumping safe-stable-stringify from 2.3.1 to 2.5.0 (a minor version bump within the existing ^2.3.1 semver range). No application source files are changed.

Security risks

None identified. safe-stable-stringify is a small, widely-used JSON serialization utility with no known CVEs in this range. The changelog between 2.3.1 and 2.5.0 lists only bug fixes (array/replacer key typing, TypedArray handling) and a new opt-in comparator option for the deterministic config — no breaking changes and nothing that expands attack surface.

Level of scrutiny

Low. This is a mechanical dependency-lock update generated by Dependabot with no code changes to review, following an established, low-risk pattern already used repeatedly in this repo's recent commit history.

Other factors

The lockfile diff is consistent with the version bump (updated version/integrity hash in both the flat and nested lockfile entries). No outstanding review comments exist on this PR.

[coveralls]

Coverage Report for CI Build 32263640280

Coverage decreased (-0.005%) to 81.175%

Details

• Coverage decreased (-0.005%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	13123
Covered Lines:	11077
Line Coverage:	84.41%
Relevant Branches:	7801
Covered Branches:	5908
Branch Coverage:	75.73%
Branches in Coverage %:	Yes
Coverage Strength:	598.09 hits per line

---

💛 - Coveralls