note when not applicable to vite plugin

Author: emily-shen

src/content/docs/workers/wrangler/configuration.mdx

@@ -61,6 +61,8 @@ The majority of keys are inheritable, meaning that top-level configuration can b
 
 Further, there are a few keys that can _only_ appear at the top-level.
 
+With the [Cloudflare Vite plugin](/workers/local-development/vite/), you select a Wrangler environment at dev or build time via the `CLOUDFLARE_ENV` environment variable. Otherwise, environments are defined in your Wrangler config file as usual. For more detail on using Wrangler environments with the Cloudflare Vite plugin, refer to the [plugin documentation](/workers/local-development/vite#environments).
+
 ## Top-level only keys
 
 Top-level keys apply to the Worker as a whole (and therefore all environments). They cannot be defined within named environments.
@@ -80,6 +82,7 @@ Top-level keys apply to the Worker as a whole (and therefore all environments).
 - `site` <Type text="object" /> <MetaInfo text="optional deprecated" />
 
   - See the [Workers Sites](#workers-sites) section below for more information. Cloudflare Pages and Workers Assets is preferred over this approach.
+  - This is not supported by the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 ## Inheritable keys
 
@@ -129,6 +132,7 @@ At a minimum, the `name`, `main` and `compatibility_date` keys are required to d
 - `tsconfig` <Type text="string" /> <MetaInfo text="optional" />
 
   - Path to a custom `tsconfig`.
+  - Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 - `triggers` <Type text="object" /> <MetaInfo text="optional" />
 
@@ -137,35 +141,43 @@ At a minimum, the `name`, `main` and `compatibility_date` keys are required to d
 - `rules` <Type text="Rule" /> <MetaInfo text="optional" />
 
   - An ordered list of rules that define which modules to import, and what type to import them as. You will need to specify rules to use `Text`, `Data` and `CompiledWasm` modules, or when you wish to have a `.js` file be treated as an `ESModule` instead of `CommonJS`.
+  - Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 - `build` <Type text="Build" /> <MetaInfo text="optional" />
 
   - Configures a custom build step to be run by Wrangler when building your Worker. Refer to [Custom builds](#custom-builds).
+  - Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 - `no_bundle` <Type text="boolean" /> <MetaInfo text="optional" />
 
   - Skip internal build steps and directly deploy your Worker script. You must have a plain JavaScript Worker with no dependencies.
+  - Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 - `find_additional_modules` <Type text="boolean" /> <MetaInfo text="optional" />
 
   - If true then Wrangler will traverse the file tree below `base_dir`.
     Any files that match `rules` will be included in the deployed Worker.
     Defaults to true if `no_bundle` is true, otherwise false.
     Can only be used with Module format Workers (not Service Worker format).
+  - Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 - `base_dir` <Type text="string" /> <MetaInfo text="optional" />
 
   - The directory in which module "rules" should be evaluated when including additional files (via `find_additional_modules`) into a Worker deployment. Defaults to the directory containing the `main` entry point of the Worker if not specified.
+  - Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 - `preserve_file_names` <Type text="boolean" /> <MetaInfo text="optional" />
 
   - Determines whether Wrangler will preserve the file names of additional modules bundled with the Worker.
     The default is to prepend filenames with a content hash.
     For example, `34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico`.
+  - Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 - `minify` <Type text="boolean" /> <MetaInfo text="optional" />
 
   - Minify the Worker script before uploading.
+  - If you're using the [Cloudflare Vite plugin](/workers/local-development/vite/), `minify` is replaced by Vite's `build.minify` - refer to the [Vite
+    documentation](https://vite.dev/config/build-options.html#build-minify).
 
 - `logpush` <Type text="boolean" /> <MetaInfo text="optional" />
 
@@ -189,6 +201,8 @@ Non-inheritable keys are configurable at the top-level, but cannot be inherited
 - `define` <Type text="Record<string, string>" /> <MetaInfo text="optional" />
 
   - A map of values to substitute when deploying your Worker.
+  - If you're using the [Cloudflare Vite plugin](/workers/local-development/vite/), this is replaced by Vite's `define` - refer to the [Vite
+    documentation](https://vite.dev/config/shared-options.html#define).
 
 - `vars` <Type text="object" /> <MetaInfo text="optional" />
 
@@ -369,6 +383,10 @@ head_sampling_rate = 0.1 # 10% of requests are logged
 
 ## Custom builds
 
+::: note
+Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
+:::
+
 You can configure a custom build step that will be run before your Worker is deployed. Refer to [Custom builds](/workers/wrangler/custom-builds/).
 
 - `command` <Type text="string" /> <MetaInfo text="optional" />
@@ -988,6 +1006,7 @@ The following options are available under the `assets` key.
 - `directory` <Type text="string" /> <MetaInfo text="required" />
 
   - Folder of static assets to be served.
+  - Not required if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/), which will automatically point to the client build output.
 
 - `binding` <Type text="string" /> <MetaInfo text="optional" />
 
@@ -1017,6 +1036,10 @@ assets = { directory = "./public", binding = "ASSETS", html_handling = "force-tr
 
 ## Bundling
 
+::: note
+Wrangler bundling is not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
+:::
+
 Wrangler can operate in two modes: the default bundling mode and `--no-bundle` mode.
 In bundling mode, Wrangler will traverse all the imports of your code and generate a single JavaScript "entry-point" file.
 Imported source code is "inlined/bundled" into this entry-point file.
@@ -1074,6 +1097,8 @@ See https://developers.cloudflare.com/workers/wrangler/bundling/ for more detail
 
 ## Local development settings
 
+Q: is this replaced by vite's server options?
+
 You can configure various aspects of local development, such as the local protocol or port.
 
 - `ip` <Type text="string" /> <MetaInfo text="optional" />
@@ -1117,10 +1142,10 @@ local_protocol = "http"
 
 ## Module Aliasing
 
-<Details header="⚡ Vite plugin">
-	This is replaced "resolve.alias" in Vite - refer to the Vite documentation for
-	usage: https://vite.dev/config/shared-options.html#resolve-alias".
-</Details>
+:::note
+If you're using the [Cloudflare Vite plugin](/workers/local-development/vite/), `alias` is replaced Vite's `resolve.alias` - refer to the [Vite
+documentation](https://vite.dev/config/shared-options.html#resolve-alias).
+:::
 
 You can configure Wrangler to replace all calls to import a particular package with a module of your choice, by configuring the `alias` field:
 
@@ -1198,6 +1223,7 @@ In many cases, this allows you to work provide just enough of an API to make a d
 - `upload_source_maps` <Type text="boolean" />
 
   - When `upload_source_maps` is set to `true`, Wrangler will automatically generate and upload source map files when you run [`wrangler deploy`](/workers/wrangler/commands/#deploy) or [`wrangler versions deploy`](/workers/wrangler/commands/#deploy-2).
+  - Not applicable if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/).
 
 Example:
 
@@ -1282,6 +1308,8 @@ This section describes a feature that can be implemented by frameworks and other
 
 It is unlikely that an application developer will need to use this feature, but it is documented here to help you understand when Wrangler is using a generated configuration rather than the original, user's configuration.
 
+For example, when you are using the [Cloudflare Vite plugin](/workers/local-development/vite/), it will generate a Wrangler configuration file when you run `vite build`, which is then used for preview and deployment.
+
 :::
 
 Some framework tools, or custom pre-build processes, generate a modified Wrangler configuration to be used to deploy the Worker code.

src/content/partials/workers/workers_sites.mdx

@@ -1,9 +1,8 @@
 ---
 {}
-
 ---
 
 :::caution[Use Workers Static Assets Instead]
 
-You should use [Workers Static Assets](/workers/static-assets/) to host full-stack applications instead of Workers Sites. Do not use Workers Sites for new projects.
+You should use [Workers Static Assets](/workers/static-assets/) to host full-stack applications instead of Workers Sites. It has been deprecated in Wrangler v4, and the [Cloudflare Vite plugin](/workers/local-development/vite) does not support Workers Sites. Do not use Workers Sites for new projects.
 :::