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)
performance-studio	✅ Ready (Inspect)	Visit Preview		Mar 24, 2025 2:21pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 24, 2025 2:21pm

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Mar 24, 2025 2:21pm
test-next-studio	⬜️ Ignored (Inspect)			Mar 24, 2025 2:21pm
page-building-studio	⬜️ Skipped (Inspect)			Mar 24, 2025 2:21pm

[github-actions]

No changes to documentation

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	43.17%	55968 / 129617
🔵	Statements	43.17%	55968 / 129617
🔵	Functions	47.29%	2779 / 5876
🔵	Branches	79.75%	10474 / 13132

File Coverage

No changed files found.

Generated in workflow #32734 for commit 5962c01 by the Vitest Coverage Report Action

[github-actions]

⚡️ Editor Performance Report

Updated Mon, 24 Mar 2025 14:30:02 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	18.0 efps (56ms)	18.9 efps (53ms)	-3ms (-4.5%)	✅
article (body)	78.1 efps (13ms)	73.3 efps (14ms)	+1ms (-/-%)	✅
article (string inside object)	20.8 efps (48ms)	18.9 efps (53ms)	+5ms (+10.4%)	✅
article (string inside array)	18.5 efps (54ms)	17.9 efps (56ms)	+2ms (+3.7%)	✅
recipe (name)	41.7 efps (24ms)	41.7 efps (24ms)	+0ms (-/-%)	✅
recipe (description)	47.6 efps (21ms)	47.6 efps (21ms)	+0ms (-/-%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (6ms)	+0ms (-/-%)	✅
synthetic (title)	16.3 efps (62ms)	18.7 efps (54ms)	-8ms (-13.0%)	✅
synthetic (string inside object)	15.9 efps (63ms)	19.6 efps (51ms)	-12ms (-19.0%)	✅

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)	56ms	62ms	73ms	261ms	1365ms	12.0s
article (body)	13ms	16ms	20ms	144ms	187ms	5.1s
article (string inside object)	48ms	52ms	55ms	79ms	913ms	8.1s
article (string inside array)	54ms	56ms	58ms	154ms	1098ms	8.5s
recipe (name)	24ms	25ms	28ms	34ms	0ms	7.6s
recipe (description)	21ms	22ms	24ms	70ms	1ms	5.0s
recipe (instructions)	6ms	8ms	9ms	11ms	0ms	3.3s
synthetic (title)	62ms	65ms	70ms	218ms	1704ms	13.5s
synthetic (string inside object)	63ms	64ms	70ms	263ms	1656ms	9.1s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	53ms	68ms	83ms	298ms	1293ms	12.5s
article (body)	14ms	15ms	23ms	45ms	66ms	5.5s
article (string inside object)	53ms	56ms	59ms	163ms	983ms	8.8s
article (string inside array)	56ms	58ms	70ms	97ms	1209ms	9.0s
recipe (name)	24ms	25ms	27ms	31ms	0ms	7.3s
recipe (description)	21ms	23ms	24ms	34ms	0ms	4.9s
recipe (instructions)	6ms	8ms	9ms	23ms	1ms	3.3s
synthetic (title)	54ms	56ms	61ms	215ms	877ms	12.6s
synthetic (string inside object)	51ms	53ms	56ms	314ms	824ms	8.6s

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

📊 Playwright Test Report

Download Full E2E Report

This report contains test results, including videos of failing tests.