chore(deps): update dependency @vitejs/plugin-react to ^4.3.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitejs/plugin-react (source)	^4.3.3 -> ^4.3.4

---

Release Notes

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v4.3.4

Compare Source

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #​386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[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	Jan 6, 2025 2:29pm
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 6, 2025 2:29pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 6, 2025 2:29pm

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Jan 6, 2025 2:29pm
test-next-studio	⬜️ Ignored (Inspect)			Jan 6, 2025 2:29pm

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Jan 6, 2025 2:37 PM (UTC)

✅ All Tests Passed -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	1m 3s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	12s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	✅ Passed (Inspect)	38s	6	0	0
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx	✅ Passed (Inspect)	51s	11	7	0
formBuilder/inputs/PortableText/copyPaste/CopyPasteFields.spec.tsx	✅ Passed (Inspect)	0s	0	12	0
formBuilder/inputs/PortableText/Decorators.spec.tsx	✅ Passed (Inspect)	25s	6	0	0
formBuilder/inputs/PortableText/DisableFocusAndUnset.spec.tsx	✅ Passed (Inspect)	14s	3	0	0
formBuilder/inputs/PortableText/DragAndDrop.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	✅ Passed (Inspect)	1m 6s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 27s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 39s	18	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	12s	3	9	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/Toolbar.spec.tsx	✅ Passed (Inspect)	1m 42s	21	0	0
formBuilder/tree-editing/TreeEditing.spec.tsx	✅ Passed (Inspect)	0s	0	3	0
formBuilder/tree-editing/TreeEditingNestedObjects.spec.tsx	✅ Passed (Inspect)	0s	0	3	0

[github-actions]

⚡️ Editor Performance Report

Updated Mon, 06 Jan 2025 14:41:26 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	23.8 efps (42ms)	25.0 efps (40ms)	-2ms (-4.8%)	✅
article (body)	48.1 efps (21ms)	50.3 efps (20ms)	-1ms (-4.3%)	✅
article (string inside object)	23.3 efps (43ms)	26.3 efps (38ms)	-5ms (-11.6%)	✅
article (string inside array)	21.3 efps (47ms)	23.3 efps (43ms)	-4ms (-8.5%)	✅
recipe (name)	47.6 efps (21ms)	52.6 efps (19ms)	-2ms (-9.5%)	✅
recipe (description)	50.0 efps (20ms)	58.8 efps (17ms)	-3ms (-15.0%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (7ms)	+1ms (-/-%)	✅
synthetic (title)	18.2 efps (55ms)	18.9 efps (53ms)	-2ms (-3.6%)	✅
synthetic (string inside object)	19.2 efps (52ms)	19.6 efps (51ms)	-1ms (-1.9%)	✅

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)	42ms	53ms	74ms	421ms	885ms	11.0s
article (body)	21ms	26ms	32ms	266ms	403ms	6.1s
article (string inside object)	43ms	47ms	60ms	77ms	367ms	7.4s
article (string inside array)	47ms	49ms	55ms	71ms	454ms	7.7s
recipe (name)	21ms	23ms	25ms	46ms	7ms	7.0s
recipe (description)	20ms	21ms	24ms	46ms	0ms	4.9s
recipe (instructions)	6ms	8ms	9ms	50ms	23ms	3.2s
synthetic (title)	55ms	58ms	66ms	144ms	1084ms	16.3s
synthetic (string inside object)	52ms	53ms	58ms	282ms	768ms	8.3s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	40ms	50ms	73ms	458ms	950ms	12.7s
article (body)	20ms	23ms	27ms	61ms	199ms	5.6s
article (string inside object)	38ms	42ms	45ms	144ms	273ms	7.5s
article (string inside array)	43ms	45ms	48ms	85ms	315ms	7.3s
recipe (name)	19ms	21ms	23ms	40ms	0ms	7.2s
recipe (description)	17ms	18ms	19ms	34ms	0ms	4.3s
recipe (instructions)	7ms	8ms	10ms	29ms	0ms	3.2s
synthetic (title)	53ms	56ms	63ms	315ms	828ms	13.4s
synthetic (string inside object)	51ms	56ms	67ms	462ms	1068ms	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.