chore: test with no compiler

[stipsan]

Description

What to review

Testing

Notes for release

[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	Sep 12, 2025 0:51am
performance-studio	Ready	Preview	Comment	Sep 12, 2025 0:51am
test-studio	Ready	Preview	Comment	Sep 12, 2025 0:51am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
e2e-studio	Ignored			Sep 12, 2025 0:51am
studio-workshop	Ignored	Preview		Sep 12, 2025 0:51am
test-next-studio	Ignored			Sep 12, 2025 0:51am

[github-actions]

⚡️ Editor Performance Report

Updated Fri, 12 Sep 2025 01:10:13 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	20.6 efps (49ms)	12.1 efps (83ms)	+34ms (+70.1%)	🔴
article (body)	45.0 efps (22ms)	41.6 efps (24ms)	+2ms (+8.3%)	✅
article (string inside object)	22.2 efps (45ms)	12.6 efps (80ms)	+35ms (+76.7%)	🔴
article (string inside array)	20.4 efps (49ms)	11.4 efps (88ms)	+39ms (+78.6%)	🔴
recipe (name)	40.0 efps (25ms)	17.2 efps (58ms)	+33ms (+132.0%)	🔴
recipe (description)	43.5 efps (23ms)	18.0 efps (56ms)	+33ms (+141.3%)	🔴
recipe (instructions)	99.9+ efps (9ms)	99.9+ efps (9ms)	+1ms (-/-%)	✅
synthetic (title)	16.4 efps (61ms)	8.2 efps (123ms)	+62ms (+100.8%)	🔴
synthetic (string inside object)	17.2 efps (58ms)	10.5 efps (96ms)	+38ms (+64.7%)	🔴

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	57ms	93ms	402ms	434ms	13.2s
article (body)	22ms	26ms	44ms	151ms	268ms	6.4s
article (string inside object)	45ms	52ms	64ms	222ms	560ms	8.1s
article (string inside array)	49ms	54ms	61ms	290ms	419ms	8.0s
recipe (name)	25ms	28ms	31ms	69ms	5ms	8.1s
recipe (description)	23ms	25ms	28ms	44ms	0ms	5.2s
recipe (instructions)	9ms	10ms	13ms	38ms	0ms	3.2s
synthetic (title)	61ms	66ms	78ms	367ms	1631ms	16.3s
synthetic (string inside object)	58ms	60ms	65ms	432ms	1536ms	8.8s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	83ms	109ms	131ms	408ms	2811ms	16.3s
article (body)	24ms	38ms	82ms	260ms	728ms	7.8s
article (string inside object)	80ms	116ms	145ms	396ms	2806ms	12.8s
article (string inside array)	88ms	114ms	131ms	309ms	2962ms	12.4s
recipe (name)	58ms	89ms	117ms	185ms	1484ms	12.9s
recipe (description)	56ms	71ms	85ms	140ms	973ms	9.0s
recipe (instructions)	9ms	11ms	37ms	108ms	77ms	3.6s
synthetic (title)	123ms	164ms	233ms	445ms	6702ms	23.8s
synthetic (string inside object)	96ms	120ms	154ms	642ms	4696ms	14.0s

📚 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-hjxmgg53f.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-hjxmgg53f.sanity.dev
  SANITY_E2E_DATASET="update depending the project you want to test (pr-10623-chromium-17661151845 || pr-10623-firefox-17661151845 )"
  SANITY_E2E_DATASET_CHROMIUM=pr-10623-chromium-17661151845
  SANITY_E2E_DATASET_FIREFOX=pr-10623-firefox-17661151845

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

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	44.79%	63636 / 142051
🔵	Statements	44.79%	63636 / 142051
🔵	Functions	49.96%	3213 / 6431
🔵	Branches	79.3%	11856 / 14950

File Coverage

No changed files found.

Generated in workflow #42182 for commit c8af0a1 by the Vitest Coverage Report Action