chore(deps): dedupe pnpm-lock.yaml

[squiggler]

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	May 5, 2025 9:24am
performance-studio	✅ Ready (Inspect)	Visit Preview		May 5, 2025 9:24am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 5, 2025 9:24am

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
e2e-studio	⬜️ Ignored (Inspect)			May 5, 2025 9:24am
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		May 5, 2025 9:24am
test-next-studio	⬜️ Ignored (Inspect)			May 5, 2025 9:24am

[github-actions]

No changes to documentation

[github-actions]

⚡️ Editor Performance Report

Updated Mon, 05 May 2025 09:34:38 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)	53.1 efps (19ms)	50.3 efps (20ms)	+1ms (+5.6%)	✅
article (string inside object)	28.2 efps (36ms)	27.0 efps (37ms)	+2ms (+4.2%)	✅
article (string inside array)	24.4 efps (41ms)	23.3 efps (43ms)	+2ms (+4.9%)	✅
recipe (name)	45.5 efps (22ms)	44.4 efps (23ms)	+1ms (+2.3%)	✅
recipe (description)	50.0 efps (20ms)	50.0 efps (20ms)	+0ms (-/-%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (6ms)	+0ms (-/-%)	✅
synthetic (title)	17.9 efps (56ms)	18.5 efps (54ms)	-2ms (-3.6%)	✅
synthetic (string inside object)	18.2 efps (55ms)	17.5 efps (57ms)	+2ms (+3.6%)	✅

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	46ms	62ms	257ms	343ms	10.5s
article (body)	19ms	22ms	33ms	180ms	318ms	5.9s
article (string inside object)	36ms	37ms	43ms	48ms	6ms	6.7s
article (string inside array)	41ms	45ms	48ms	255ms	335ms	7.5s
recipe (name)	22ms	24ms	29ms	43ms	0ms	8.3s
recipe (description)	20ms	24ms	27ms	37ms	0ms	5.2s
recipe (instructions)	6ms	9ms	10ms	26ms	0ms	3.2s
synthetic (title)	56ms	61ms	66ms	327ms	1265ms	14.5s
synthetic (string inside object)	55ms	60ms	70ms	522ms	1235ms	9.0s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	38ms	40ms	49ms	92ms	54ms	9.8s
article (body)	20ms	23ms	31ms	213ms	274ms	5.6s
article (string inside object)	37ms	40ms	46ms	232ms	255ms	7.2s
article (string inside array)	43ms	46ms	58ms	238ms	296ms	7.5s
recipe (name)	23ms	24ms	32ms	49ms	0ms	8.8s
recipe (description)	20ms	23ms	30ms	57ms	0ms	5.1s
recipe (instructions)	6ms	8ms	10ms	12ms	0ms	3.1s
synthetic (title)	54ms	57ms	63ms	249ms	871ms	14.1s
synthetic (string inside object)	57ms	59ms	63ms	203ms	1036ms	8.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.

[github-actions]

🧪 E2E Preview environment

🔑 Environment Variables for Local Testing

This is the preview URL for the E2E tests: https://e2e-studio-mffw6wrln.sanity.dev

To run the E2E tests locally, you can use the following environment variables, then run pnpm test:e2e --ui to open the Playwright test runner.

💬 Remember to build the project first with pnpm build:e2e.

  SANITY_E2E_PROJECT_ID=ittbm412
  SANITY_E2E_BASE_URL=https://e2e-studio-mffw6wrln.sanity.dev
  SANITY_E2E_DATASET="update depending the project you want to test (pr-9337-chromium-14833113186 || pr-9337-firefox-14833113186 )"
  SANITY_E2E_DATASET_CHROMIUM=pr-9337-chromium-14833113186
  SANITY_E2E_DATASET_FIREFOX=pr-9337-firefox-14833113186

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	43.26%	57657 / 133272
🔵	Statements	43.26%	57657 / 133272
🔵	Functions	47.7%	2880 / 6037
🔵	Branches	79.61%	10720 / 13464

File Coverage

No changed files found.

Generated in workflow #34620 for commit 412531e by the Vitest Coverage Report Action

[github-actions]

📊 Playwright Test Report

Download Full E2E Report

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