fix(deps): update dependency react-rx to ^4.1.18

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-rx (source)	^4.1.17 -> ^4.1.18

---

Release Notes

sanity-io/react-rx (react-rx)

v4.1.18

Compare Source

Bug Fixes

• deps: update React Compiler dependencies 🤖 ✨ (#​219) (5ac12e2)

---

Configuration

📅 Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
page-building-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 4, 2025 10:46am
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 4, 2025 10:46am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 4, 2025 10:46am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Feb 4, 2025 10:46am
test-next-studio	⬜️ Ignored (Inspect)			Feb 4, 2025 10:46am

[socket-security]

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: npm/[email protected]

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Feb 4, 2025 10:49 AM (UTC)

❌ Failed Tests (1) -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	1m 6s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	12s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	❌ Failed (Inspect)	1m 20s	5	0	1
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx	✅ Passed (Inspect)	51s	11	7	0
formBuilder/inputs/PortableText/copyPaste/CopyPasteFields.spec.tsx	✅ Passed (Inspect)	0s	0	12	0
formBuilder/inputs/PortableText/Decorators.spec.tsx	✅ Passed (Inspect)	25s	6	0	0
formBuilder/inputs/PortableText/DisableFocusAndUnset.spec.tsx	✅ Passed (Inspect)	14s	3	0	0
formBuilder/inputs/PortableText/DragAndDrop.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	✅ Passed (Inspect)	1m 6s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 28s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	2m 1s	21	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	12s	3	9	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/Toolbar.spec.tsx	✅ Passed (Inspect)	1m 43s	21	0	0
formBuilder/tree-editing/TreeEditing.spec.tsx	✅ Passed (Inspect)	0s	0	3	0
formBuilder/tree-editing/TreeEditingNestedObjects.spec.tsx	✅ Passed (Inspect)	0s	0	3	0

[github-actions]

⚡️ Editor Performance Report

Updated Tue, 04 Feb 2025 10:51:52 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	25.6 efps (39ms)	26.3 efps (38ms)	-1ms (-2.6%)	✅
article (body)	67.6 efps (15ms)	72.5 efps (14ms)	-1ms (-/-%)	✅
article (string inside object)	27.0 efps (37ms)	27.8 efps (36ms)	-1ms (-2.7%)	✅
article (string inside array)	23.8 efps (42ms)	25.0 efps (40ms)	-2ms (-4.8%)	✅
recipe (name)	50.0 efps (20ms)	52.6 efps (19ms)	-1ms (-5.0%)	✅
recipe (description)	58.8 efps (17ms)	58.8 efps (17ms)	+0ms (-/-%)	✅
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (6ms)	+1ms (-/-%)	✅
synthetic (title)	19.6 efps (51ms)	20.0 efps (50ms)	-1ms (-2.0%)	✅
synthetic (string inside object)	19.6 efps (51ms)	20.2 efps (50ms)	-2ms (-2.9%)	✅

efps — editor "frames per second". The number of updates assumed to be possible within a second.

Derived from input latency. efps = 1000 / input_latency

Detailed information

🏠 Reference result

The performance result of sanity@latest

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	39ms	43ms	53ms	417ms	197ms	10.1s
article (body)	15ms	17ms	25ms	109ms	311ms	5.3s
article (string inside object)	37ms	40ms	51ms	300ms	395ms	6.9s
article (string inside array)	42ms	44ms	48ms	97ms	368ms	7.0s
recipe (name)	20ms	22ms	25ms	59ms	1ms	7.2s
recipe (description)	17ms	19ms	20ms	34ms	0ms	4.4s
recipe (instructions)	5ms	6ms	7ms	8ms	0ms	3.1s
synthetic (title)	51ms	54ms	62ms	182ms	777ms	12.9s
synthetic (string inside object)	51ms	57ms	77ms	300ms	740ms	8.7s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	38ms	46ms	69ms	451ms	882ms	10.3s
article (body)	14ms	16ms	28ms	146ms	449ms	5.7s
article (string inside object)	36ms	39ms	41ms	176ms	260ms	6.6s
article (string inside array)	40ms	42ms	52ms	148ms	264ms	6.8s
recipe (name)	19ms	21ms	24ms	41ms	0ms	7.1s
recipe (description)	17ms	18ms	20ms	29ms	0ms	4.4s
recipe (instructions)	6ms	7ms	11ms	21ms	0ms	3.1s
synthetic (title)	50ms	55ms	58ms	306ms	723ms	18.3s
synthetic (string inside object)	50ms	52ms	57ms	280ms	529ms	7.9s

📚 Glossary

column definitions

• benchmark — the name of the test, e.g. "article", followed by the label of the field being measured, e.g. "(title)".
• latency — the time between when a key was pressed and when it was rendered. derived from a set of samples. the median (p50) is shown to show the most common latency.
• p75 — the 75th percentile of the input latency in the test run. 75% of the sampled inputs in this benchmark were processed faster than this value. this provides insight into the upper range of typical performance.
• p90 — the 90th percentile of the input latency in the test run. 90% of the sampled inputs were faster than this. this metric helps identify slower interactions that occurred less frequently during the benchmark.
• p99 — the 99th percentile of the input latency in the test run. only 1% of sampled inputs were slower than this. this represents the worst-case scenarios encountered during the benchmark, useful for identifying potential performance outliers.
• blocking time — the total time during which the main thread was blocked, preventing user input and UI updates. this metric helps identify performance bottlenecks that may cause the interface to feel unresponsive.
• test duration — how long the test run took to complete.