chore(tests): generate dts tests 🤖 ✨

[squiggler]

I ran pnpm generate:dts-exports 🧑‍💻. If you need to investigate where new imports are coming from run TEST_DTS_EXPORTS_DIAGNOSTICS=full pnpm generate:dts-exports 💡

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
page-building-studio	Ready	Preview	Comment	Oct 23, 2025 11:57am
performance-studio	Ready	Preview	Comment	Oct 23, 2025 11:57am
test-studio	Ready	Preview	Comment	Oct 23, 2025 11:57am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
e2e-studio	Ignored			Oct 23, 2025 11:57am
studio-workshop	Ignored	Preview		Oct 23, 2025 11:57am
test-next-studio	Ignored			Oct 23, 2025 11:57am

[github-actions]

🧪 E2E Preview environment

🔑 Environment Variables for Local Testing

This is the preview URL for the E2E tests: https://e2e-studio-pafrxwqje.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-pafrxwqje.sanity.dev
  SANITY_E2E_DATASET="update depending the project you want to test (pr-10903-chromium-18747367542 || pr-10903-firefox-18747367542 )"
  SANITY_E2E_DATASET_CHROMIUM=pr-10903-chromium-18747367542
  SANITY_E2E_DATASET_FIREFOX=pr-10903-firefox-18747367542

[github-actions]

📊 Playwright Test Report

Download Full E2E Report

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

[github-actions]

No changes to documentation

[github-actions]

⚡️ Editor Performance Report

Updated Thu, 23 Oct 2025 12:21:49 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	11.8 efps (85ms)	12.3 efps (81ms)	-4ms (-4.1%)	✅
article (body)	35.0 efps (29ms)	29.8 efps (34ms)	+5ms (+17.5%)	✅
article (string inside object)	13.3 efps (75ms)	12.7 efps (79ms)	+4ms (+5.3%)	✅
article (string inside array)	12.1 efps (83ms)	12.3 efps (82ms)	-1ms (-1.2%)	✅
recipe (name)	18.2 efps (55ms)	18.2 efps (55ms)	+0ms (-/-%)	✅
recipe (description)	19.8 efps (51ms)	19.2 efps (52ms)	+2ms (+3.0%)	✅
recipe (instructions)	99.9+ efps (7ms)	99.9+ efps (8ms)	+1ms (-/-%)	✅
singleString (stringField)	31.3 efps (32ms)	30.3 efps (33ms)	+1ms (+3.1%)	✅
synthetic (title)	8.4 efps (119ms)	8.4 efps (120ms)	+1ms (+0.4%)	✅
synthetic (string inside object)	10.0 efps (100ms)	9.3 efps (108ms)	+8ms (+7.5%)	✅

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)	85ms	116ms	213ms	320ms	3160ms	18.1s
article (body)	29ms	64ms	154ms	342ms	1309ms	9.9s
article (string inside object)	75ms	93ms	171ms	389ms	2617ms	11.6s
article (string inside array)	83ms	97ms	125ms	303ms	2563ms	11.9s
recipe (name)	55ms	72ms	93ms	177ms	1209ms	12.5s
recipe (description)	51ms	68ms	101ms	172ms	1049ms	8.9s
recipe (instructions)	7ms	13ms	31ms	126ms	85ms	3.9s
singleString (stringField)	32ms	39ms	51ms	70ms	72ms	8.6s
synthetic (title)	119ms	165ms	238ms	376ms	5632ms	24.5s
synthetic (string inside object)	100ms	121ms	206ms	331ms	4011ms	14.0s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	81ms	103ms	180ms	489ms	3136ms	18.2s
article (body)	34ms	51ms	168ms	331ms	1465ms	10.7s
article (string inside object)	79ms	97ms	135ms	449ms	2804ms	12.9s
article (string inside array)	82ms	107ms	161ms	450ms	2880ms	12.4s
recipe (name)	55ms	72ms	95ms	150ms	1201ms	11.9s
recipe (description)	52ms	70ms	103ms	122ms	1082ms	9.0s
recipe (instructions)	8ms	11ms	17ms	118ms	88ms	3.6s
singleString (stringField)	33ms	42ms	51ms	78ms	28ms	8.9s
synthetic (title)	120ms	208ms	244ms	402ms	5568ms	25.5s
synthetic (string inside object)	108ms	137ms	190ms	438ms	4284ms	14.1s

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

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	44.83%	64419 / 143665
🔵	Statements	44.83%	64419 / 143665
🔵	Functions	49.87%	3239 / 6494
🔵	Branches	79.46%	12065 / 15183

File Coverage

No changed files found.

Generated in workflow #43986 for commit d2eb632 by the Vitest Coverage Report Action