From a991511d137e87b615aed06f15acbc0ea7e0721c Mon Sep 17 00:00:00 2001
From: Ryan Christian <33403762+rschristian@users.noreply.github.com>
Date: Tue, 6 Aug 2024 19:04:22 -0500
Subject: [PATCH] docs: Explicitly note preset-vite in alias prelude

---
 content/en/guide/v10/getting-started.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/guide/v10/getting-started.md b/content/en/guide/v10/getting-started.md
index 1bdb608d3..758f52634 100644
--- a/content/en/guide/v10/getting-started.md
+++ b/content/en/guide/v10/getting-started.md
@@ -133,7 +133,7 @@ To transpile JSX, you need a Babel plugin that converts it to valid JavaScript c
 
 At some point, you'll probably want to make use of the vast React ecosystem. Libraries and Components originally written for React work seamlessly with our compatibility layer. To make use of it, we need to point all `react` and `react-dom` imports to Preact. This step is called _aliasing._
 
-> **Note:** If you're using Vite, Preact CLI, or WMR, these aliases are automatically handled for you by default.
+> **Note:** If you're using Vite (via `@preact/preset-vite`), Preact CLI, or WMR, these aliases are automatically handled for you by default.
 
 #### Aliasing in Webpack