chore: test rolldown-vite ⚡️

[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	Dec 2, 2025 11:27am
test-studio	Ready	Preview	Comment	Dec 2, 2025 11:27am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
e2e-studio	Ignored			Dec 2, 2025 11:27am
studio-workshop	Ignored	Preview		Dec 2, 2025 11:27am
test-next-studio	Ignored			Dec 2, 2025 11:27am

[github-actions]

🧪 E2E Preview environment

🔑 Environment Variables for Local Testing

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

[github-actions]

📊 Playwright Test Report

Download Full E2E Report

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​rolldown-vite@​7.2.8

View full report

[github-actions]

⚡️ Editor Performance Report

Updated Tue, 02 Dec 2025 11:39:08 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	25.6 efps (39ms)	24.4 efps (41ms)	+2ms (+5.1%)	✅
article (body)	36.0 efps (28ms)	36.7 efps (27ms)	-0ms (-1.8%)	✅
article (string inside object)	28.6 efps (35ms)	27.8 efps (36ms)	+1ms (+2.9%)	✅
article (string inside array)	25.0 efps (40ms)	24.4 efps (41ms)	+1ms (+2.5%)	✅
recipe (name)	41.7 efps (24ms)	41.7 efps (24ms)	+0ms (-/-%)	✅
recipe (description)	62.5 efps (16ms)	55.6 efps (18ms)	+2ms (+12.5%)	✅
recipe (instructions)	99.9+ efps (9ms)	99.9+ efps (8ms)	-1ms (-/-%)	✅
singleString (stringField)	52.6 efps (19ms)	51.3 efps (20ms)	+1ms (+2.6%)	✅
synthetic (title)	16.1 efps (62ms)	16.7 efps (60ms)	-2ms (-3.2%)	✅
synthetic (string inside object)	17.2 efps (58ms)	16.9 efps (59ms)	+1ms (+1.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)	39ms	42ms	55ms	130ms	46ms	9.8s
article (body)	28ms	34ms	79ms	135ms	127ms	6.4s
article (string inside object)	35ms	38ms	43ms	86ms	0ms	5.7s
article (string inside array)	40ms	43ms	48ms	102ms	0ms	6.1s
recipe (name)	24ms	26ms	43ms	54ms	0ms	7.0s
recipe (description)	16ms	19ms	20ms	21ms	0ms	4.2s
recipe (instructions)	9ms	10ms	12ms	13ms	0ms	3.1s
singleString (stringField)	19ms	21ms	23ms	34ms	0ms	6.4s
synthetic (title)	62ms	66ms	110ms	133ms	529ms	15.3s
synthetic (string inside object)	58ms	65ms	124ms	263ms	589ms	8.1s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	41ms	46ms	79ms	111ms	31ms	9.8s
article (body)	27ms	36ms	82ms	182ms	160ms	6.5s
article (string inside object)	36ms	39ms	42ms	120ms	13ms	5.8s
article (string inside array)	41ms	44ms	60ms	100ms	0ms	6.2s
recipe (name)	24ms	27ms	31ms	67ms	0ms	7.3s
recipe (description)	18ms	21ms	23ms	55ms	0ms	4.4s
recipe (instructions)	8ms	10ms	13ms	30ms	0ms	3.1s
singleString (stringField)	20ms	22ms	23ms	30ms	0ms	6.4s
synthetic (title)	60ms	64ms	69ms	143ms	325ms	14.1s
synthetic (string inside object)	59ms	67ms	119ms	248ms	586ms	8.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.