chore(deps): dedupe pnpm-lock.yaml

[ecospark]

I ran pnpm dedupe 🧑‍💻

[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	Jan 14, 2025 11:14am
performance-studio	✅ Ready (Inspect)	Visit Preview		Jan 14, 2025 11:14am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 14, 2025 11:14am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Jan 14, 2025 11:14am
test-next-studio	⬜️ Ignored (Inspect)			Jan 14, 2025 11:14am

[github-actions]

No changes to documentation

[github-actions]

⚡️ Editor Performance Report

Updated Tue, 14 Jan 2025 11:19:02 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	20.4 efps (49ms)	22.7 efps (44ms)	-5ms (-10.2%)	✅
article (body)	56.5 efps (18ms)	59.5 efps (17ms)	-1ms (-5.1%)	✅
article (string inside object)	23.8 efps (42ms)	25.0 efps (40ms)	-2ms (-4.8%)	✅
article (string inside array)	20.4 efps (49ms)	21.3 efps (47ms)	-2ms (-4.1%)	✅
recipe (name)	50.0 efps (20ms)	52.6 efps (19ms)	-1ms (-5.0%)	✅
recipe (description)	55.6 efps (18ms)	58.8 efps (17ms)	-1ms (-5.6%)	✅
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (6ms)	+1ms (-/-%)	✅
synthetic (title)	18.3 efps (55ms)	17.9 efps (56ms)	+2ms (+2.8%)	✅
synthetic (string inside object)	18.9 efps (53ms)	18.9 efps (53ms)	+0ms (-/-%)	✅

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)	49ms	68ms	77ms	516ms	915ms	12.6s
article (body)	18ms	20ms	32ms	97ms	261ms	6.0s
article (string inside object)	42ms	44ms	54ms	169ms	151ms	7.0s
article (string inside array)	49ms	52ms	53ms	63ms	204ms	7.3s
recipe (name)	20ms	22ms	24ms	42ms	0ms	7.9s
recipe (description)	18ms	19ms	22ms	44ms	0ms	4.6s
recipe (instructions)	5ms	6ms	7ms	8ms	0ms	3.0s
synthetic (title)	55ms	59ms	75ms	176ms	765ms	13.1s
synthetic (string inside object)	53ms	56ms	61ms	478ms	1033ms	8.6s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	44ms	52ms	79ms	482ms	992ms	11.6s
article (body)	17ms	20ms	22ms	165ms	248ms	6.0s
article (string inside object)	40ms	42ms	46ms	148ms	151ms	7.0s
article (string inside array)	47ms	49ms	55ms	175ms	243ms	7.3s
recipe (name)	19ms	20ms	23ms	33ms	0ms	6.7s
recipe (description)	17ms	19ms	22ms	27ms	0ms	4.5s
recipe (instructions)	6ms	7ms	8ms	19ms	0ms	3.1s
synthetic (title)	56ms	59ms	66ms	265ms	1071ms	13.5s
synthetic (string inside object)	53ms	56ms	65ms	479ms	1123ms	9.2s

📚 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.

[github-actions]

Component Testing Report Updated Jan 14, 2025 11:19 AM (UTC)

✅ All Tests Passed -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	1m 5s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	12s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	✅ Passed (Inspect)	39s	6	0	0
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx	✅ Passed (Inspect)	50s	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 27s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 39s	18	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	13s	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