[dependabot]

Bumps the dependencies group with 1 update: safe-stable-stringify.

Updates safe-stable-stringify from 2.5.0 to 3.0.0

Release notes

Sourced from safe-stable-stringify's releases.

v3.0.0

Breaking changes

• Require Node.js 18 or later (older versions will likely still work but are not supported).
• Changed the default circular marker to '[Circular: N]', where N is the referenced ancestor's depth, starting at 0 for the root. Set circularValue: '[Circular]' to retain the previous format. This changes the serialized output for circular references.

Features

• Added 'string' as possible bigint option value. Bigint values are serialized as JSON strings using it.

import { configure } from 'safe-stable-stringify'
const stringify = configure({
bigint: 'string'
})
stringify([1n, 2, 3n, 4, 5n])
// '["1",2,"3",4,"5"]'

• Added safe option to not fail in case a getter, .toJSON(), or a replacer throws an error. Instead, a string as error message is replacing the object inspection. This allows to partially inspect such objects. The default is false to prevent any breaking change.

import { configure } from 'safe-stable-stringify'
const stringify = configure({
safe: true
})
stringify([{
foo: { a: 5, get foo() { throw new Error('Oops') }, c: true }
}])
// '[{"foo":"Error: Stringification failed. Message: Oops"}]'
stringify([{
foo: { a: 5, toJSON() { throw new Error('Oops') }, c: true }
}])
// '[{"foo":"Error: Stringification failed. Message: Oops"}]'

Fixes

• Fixed ESM imports in Node.js and bundlers, including applications that also use CommonJS.
• Fixed off by one error using the maximumBreadth option. It showed one entry to few being skipped.
• Fixed throwing on a negative spacer number
• Fixed serializing non-finite floating-point typed array values (e.g., new Float32Array([Infinity]))

... (truncated)

Changelog

Sourced from safe-stable-stringify's changelog.

Changelog

Next

• Breaking change: Require Node.js 18 or later.

• Fix ESM imports in Node.js and bundlers, including applications that also use CommonJS.

• Changed the default circular marker to '[Circular: N]', where N is the referenced ancestor's depth, starting at 0 for the root. Set circularValue: '[Circular]' to retain the previous format. This changes the serialized output for circular references.

• Added 'string' as possible bigint option value. Bigint values are serialized as JSON strings using it.

import { configure } from 'safe-stable-stringify'
const stringify = configure({
bigint: 'string'
})
stringify([1n, 2, 3n, 4, 5n])
// '["1",2,"3",4,"5"]'

• Fixed off by one error using the maximumBreadth option. It showed one entry to few being skipped.
• Added safe option to not fail in case a getter, .toJSON(), or a replacer throws an error. Instead, a string as error message is replacing the object inspection. This allows to partially inspect such objects. The default is false to prevent any breaking change.

import { configure } from 'safe-stable-stringify'
const stringify = configure({
safe: true
})
stringify([{
foo: { a: 5, get foo() { throw new Error('Oops') }, c: true }
}])
// '[{"foo":"Error: Stringification failed. Message: Oops"}]'
stringify([{
foo: { a: 5, toJSON() { throw new Error('Oops') }, c: true }
}])
// '[{"foo":"Error: Stringification failed. Message: Oops"}]'

Commits

• bdd585f perf: reduce primitive serialization overhead (#77)
• c05878f feat(modules)!: share ESM and CommonJS exports (#72)
• 8ed2781 perf(sort): bound insertion sort work (#76)
• e8e5b3b perf(arrays): defer index string conversion (#75)
• 5dd026c docs(circular): clarify JSON escaping for custom markers (#74)
• 25b3110 fix(typed-array): serialize non-finite floating-point values (#73)
• 318cf4f feat(circular)!: include ancestor depth in default markers (#70)
• a8df6a1 fix: enforce maximumDepth for nested objects with array replacers (#64)
• 0c2253c Fix merge conflict in readme (#63)
• b8aad14 fix: do not throw on a negative number space (#65)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions