withastro
astro
BlogDocsChangelog

fix: Remove Vitest workaround for client-side Astro component rendering

#14914
Comparing
saikumarvasa100-hash:fix/remove-vitest-client-workaround
(
69cca4c
) with
main
(
bc0a4d7
)
CodSpeed Performance Gauge
0%
Untouched
6

Benchmarks

Passed

Rendering: streaming [true], .astro file
benchmark/bench/codspeed.bench.js::Bench rendering
CodSpeed Performance Gauge
0%
938.8 ms935.3 ms
Rendering: streaming [false], .md file
benchmark/bench/codspeed.bench.js::Bench rendering
CodSpeed Performance Gauge
0%
12.9 ms12.8 ms
Rendering: streaming [true], .md file
benchmark/bench/codspeed.bench.js::Bench rendering
CodSpeed Performance Gauge
0%
12.8 ms12.8 ms
Rendering: streaming [true], .mdx file
benchmark/bench/codspeed.bench.js::Bench rendering
CodSpeed Performance Gauge
0%
722.4 ms722.4 ms
Rendering: streaming [false], .mdx file
benchmark/bench/codspeed.bench.js::Bench rendering
CodSpeed Performance Gauge
0%
714.1 ms717.5 ms
Rendering: streaming [false], .astro file
benchmark/bench/codspeed.bench.js::Bench rendering
CodSpeed Performance Gauge
-3%
894.1 ms921.3 ms

Commits

Click on a commit to change the comparison range
Base
main
bc0a4d7
-0.49%
fix: Remove Vitest workaround for client-side Astro component rendering Removes the temporary workaround that allowed Vitest tests to render Astro components in a "client" environment. This is a breaking change that requires users testing Astro component rendering with the container API in Vitest to use an SSR test environment (e.g., `node`) instead of client environments like `happy-dom` or `jsdom`. Fixes #14895
69cca4c
12 hours ago
by saikumarvasa100-hash
© 2025 CodSpeed Technology
Home Terms Privacy Docs