Initial PR feedback

Author: jamesopstad

src/content/docs/workers/vite-plugin/api.mdx

@@ -7,7 +7,7 @@ sidebar:
 description: Vite plugin API
 ---
 
-### `cloudflare`
+### `cloudflare()`
 
 The `cloudflare` plugin should be included in the Vite `plugins` array:
 
@@ -29,38 +29,41 @@ It accepts an optional `PluginConfig` parameter.
 - `configPath?: string`
 
   An optional path to your Worker config file.
-  By default, a `wrangler.toml`, `wrangler.json`, or `wrangler.jsonc` file in the root of your application will be used as the Worker config.
+  By default, a `wrangler.jsonc`, `wrangler.json`, or `wrangler.toml` file in the root of your application will be used as the Worker config.
 
 - `viteEnvironment?: { name?: string }`
 
   Optional Vite environment options.
   By default, the environment name is the Worker name with `-` characters replaced with `_`.
   Setting the name here will override this.
   A typical use case is setting `viteEnvironment: { name: "ssr" }` to apply the Worker to the SSR environment.
+  See [Vite Environments](/workers/vite-plugin/vite-environments/) for more information.
 
 - `persistState?: boolean | { path: string }`
 
   An optional override for state persistence.
-  By default, state is persisted to `.wrangler/state` in a `v3` subdirectory.
+  By default, state is persisted to `.wrangler/state`.
   A custom `path` can be provided or, alternatively, persistence can be disabled by setting the value to `false`.
 
 - `inspectorPort?: number | false`
 
-  An optional inspector port to use for debugging your Workers.
-  The default value is `9229`.
-  Setting this to `false` will disable the debugging inspector.
+  An optional override for debugging your Workers.
+  By default, the debugging inspector is enabled and listens on port `9229`.
+  A custom port can be provided or, alternatively, setting this to `false` will disable the debugging inspector.
+  See [Debugging](/workers/vite-plugin/debugging/) for more information.
 
 - `auxiliaryWorkers?: Array<AuxiliaryWorkerConfig>`
 
   An optional array of auxiliary Workers.
+  Auxiliary Workers are additional Workers that are used as part of your application.
   You can use [service bindings](/workers/runtime-apis/bindings/service-bindings/) to call auxiliary Workers from your main (entry) Worker.
   All requests are routed through your entry Worker.
   During the build, each Worker is output to a separate subdirectory of `dist`.
 
 :::note
 When running `wrangler deploy`, only your main (entry) Worker will be deployed.
-If using multiple Workers, each must be deployed individually.
-You can inspect the `dist` directory and then run `wrangler deploy -c path-to-worker-output-config` for each.
+If using multiple Workers, each auxiliary Worker must be deployed individually.
+You can inspect the `dist` directory and then run `wrangler deploy -c dist/<auxiliary-worker>/wrangler.json` for each.
 :::
 
 ### `interface AuxiliaryWorkerConfig`
@@ -74,3 +77,4 @@ You can inspect the `dist` directory and then run `wrangler deploy -c path-to-wo
   Optional Vite environment options.
   By default, the environment name is the Worker name with `-` characters replaced with `_`.
   Setting the name here will override this.
+  See [Vite Environments](/workers/vite-plugin/vite-environments/) for more information.

src/content/docs/workers/vite-plugin/cloudflare-environments.mdx

@@ -3,7 +3,7 @@ pcx_content_type: reference
 title: Cloudflare Environments
 head: []
 sidebar:
-  order: 6
+  order: 9
 description: Using Cloudflare environments with the Vite plugin
 ---
 

src/content/docs/workers/vite-plugin/debugging.mdx

@@ -3,7 +3,7 @@ pcx_content_type: reference
 title: Debugging
 head: []
 sidebar:
-  order: 8
+  order: 5
 description: Debugging with the Vite plugin
 ---
 

src/content/docs/workers/vite-plugin/get-started.mdx

@@ -52,6 +52,10 @@ export default defineConfig({
 });
 ```
 
+The Cloudflare Vite plugin doesn't require any configuration by default and will look for a `wrangler.jsonc`, `wrangler.json` or `wrangler.toml` in the root of your application.
+
+Refer to the [API reference](/workers/vite-plugin/api/) for configuration options.
+
 ### Create your Worker config file
 
 <WranglerConfig>
@@ -64,6 +68,12 @@ main = "./src/index.ts"
 
 </WranglerConfig>
 
+The `name` field specifies the name of your Worker.
+By default, this is also used as the name of the Worker's Vite Environment (see [Vite Environments](/workers/vite-plugin/vite-environments/) for more information).
+The `main` field specifies the entry file for your Worker code.
+
+For more information about the Worker configuration, see [Configuration](/workers/wrangler/configuration/).
+
 ### Create your Worker entry file
 
 ```ts
@@ -76,4 +86,8 @@ export default {
 };
 ```
 
-You can now develop (`npm run dev`), build (`npm run build`), preview (`npm run preview`), and deploy (`npm run deploy`) your application.
+A request to this Worker will return 'Running in Cloudflare-Workers!', demonstrating that the code is running inside the Workers runtime.
+
+### Dev, build, preview and deploy
+
+You can now start the Vite development server (`npm run dev`), build the application (`npm run build`), preview the built application (`npm run preview`), and deploy to Cloudflare (`npm run deploy`).

src/content/docs/workers/vite-plugin/index.mdx

@@ -22,7 +22,7 @@ Your Worker code runs inside [workerd](https://github.com/cloudflare/workerd), m
 ### Use cases
 
 - React Router v7 (support for more full-stack frameworks is coming soon)
-- Single-page applications (SPAs), with or without an integrated backend API
+- Static sites, such as single-page applications, with or without an integrated backend API
 - Standalone Workers
 - Multi-Worker applications
 

src/content/docs/workers/vite-plugin/migrating-from-wrangler-dev.mdx

@@ -3,7 +3,7 @@ pcx_content_type: reference
 title: Migrating from wrangler dev
 head: []
 sidebar:
-  order: 9
+  order: 6
 description: Migrating from wrangler dev to the Vite plugin
 ---
 

src/content/docs/workers/vite-plugin/static-assets.mdx

@@ -3,7 +3,7 @@ pcx_content_type: reference
 title: Static Assets
 head: []
 sidebar:
-  order: 5
+  order: 4
 description: Static assets and the Vite plugin
 ---
 

src/content/docs/workers/vite-plugin/tutorial.mdx

@@ -14,6 +14,7 @@ Much of the content can also be applied to adapting existing Vite projects and t
 
 :::note
 If you want to start a new app with a template already set up with Vite, React and the Cloudflare Vite plugin, refer to the [React framework guide](/workers/frameworks/framework-guides/react/).
+To create a standalone Worker, refer to [Get started](/workers/vite-plugin/get-started/).
 :::
 
 ### Introduction
@@ -69,10 +70,11 @@ assets = { not_found_handling = "single-page-application" }
 The [`not_found_handling`](/workers/static-assets/routing/#not_found_handling--404-page--single-page-application--none) value has been set to `single-page-application`.
 This means that all not found requests will serve the `index.html` file.
 With the Cloudflare plugin, the `assets` routing configuration is used in place of Vite's default behavior.
-This ensures that your application's routing works the same way while developing as it does when deployed to production.
+This ensures that your application's [routing configuration](/workers/static-assets/routing/#routing-configuration) works the same way while developing as it does when deployed to production.
 
 Note that the [`directory`](/workers/static-assets/binding/#directory) field is not used when configuring assets with Vite.
 The `directory` in the output configuration will automatically point to the client build output.
+See [Static Assets](/workers/vite-plugin/static-assets/) for more information.
 
 :::note
 When using the Cloudflare Vite plugin, the Worker config (for example, `wrangler.jsonc`) that you provide is the input configuration file.
@@ -93,10 +95,10 @@ Add the following lines to your `.gitignore` file:
 
 #### Run the development server
 
-Run `npm run dev` to verify that your application is working as expected.
+Run `npm run dev` to start the Vite development server and verify that your application is working as expected.
 
 For a purely front-end application, you could now build (`npm run build`), preview (`npm run preview`), and deploy (`npm exec wrangler deploy`) your application.
-However, this tutorial will show you how to go a step further and add an API Worker.
+This tutorial, however, will show you how to go a step further and add an API Worker.
 
 ### Add an API Worker
 
@@ -113,7 +115,7 @@ However, this tutorial will show you how to go a step further and add an API Wor
 		"tsBuildInfoFile": "./node_modules/.tmp/tsconfig.worker.tsbuildinfo",
 		"types": ["@cloudflare/workers-types/2023-07-01", "vite/client"],
 	},
-	"include": ["api"],
+	"include": ["worker"],
 }
 ```
 
@@ -138,14 +140,17 @@ However, this tutorial will show you how to go a step further and add an API Wor
 name = "cloudflare-vite-tutorial"
 compatibility_date = "2024-12-30"
 assets = { not_found_handling = "single-page-application" }
-main = "./api/index.ts"
+main = "./worker/index.ts"
 ```
 
 </WranglerConfig>
+
+Setting the `not_found_handling` to `single-page-application` means that navigation requests that do not match a static asset will always return the `index.html` file.
+
 #### Add your API Worker
 
 ```ts
-// api/index.ts
+// worker/index.ts
 
 interface Env {
 	ASSETS: Fetcher;
@@ -169,8 +174,10 @@ export default {
 The Worker above will be invoked for any non-navigation request that does not match a static asset.
 It returns a JSON response if the `pathname` starts with `/api/` and otherwise return a `404` response.
 
-Browser navigations will invoke the `not_found_handling` behavior defined in the Worker config.
-As we have set this to `single-page-application`, the `index.html` file is always returned.
+:::note
+For top-level navigation requests, browsers send a `Sec-Fetch-Mode: navigate` header.
+If this is present and the URL does not match a static asset, the `not_found_handling` behavior will be invoked rather than the Worker.
+:::
 
 #### Call the API from the client
 
@@ -247,8 +254,10 @@ With Vite and the Cloudflare plugin, you can iterate on the client and server pa
 
 Run `npm run build` to build your application.
 
-If you inspect the `dist` directory, you will see that it contains two subdirectories: `client` and `cloudflare-vite-tutorial`.
-The `cloudflare-vite-tutorial` directory contains your Worker code and the output `wrangler.json` configuration.
+If you inspect the `dist` directory, you will see that it contains two subdirectories:
+
+- `client` - the client code that runs in the browser
+- `cloudflare-vite-tutorial` - the Worker code and the output `wrangler.json` Worker configuration
 
 #### Preview your application
 
@@ -262,10 +271,12 @@ This command will automatically use the output `wrangler.json` that was included
 
 ### Next steps
 
-In this tutorial, we created an SPA that could be deployed as a Worker with Workers Assets.
-We then added an API Worker that could be accessed from the front-end code and deployed to Cloudflare.
+In this tutorial, we created an SPA that could be deployed as a Worker with static assets.
+We then added an API Worker that could be accessed from the front-end code.
+Finally, we deployed both the client and server-side parts of the application to Cloudflare.
+
 Possible next steps include:
 
 - Adding a binding to another Cloudflare service such as a [KV namespace](/kv/) or [D1 database](/d1/)
 - Expanding the API to include additional routes
-- Using a library, such as [tRPC](https://trpc.io/) or [Hono](https://hono.dev/), in your API Worker
+- Using a library, such as [Hono](https://hono.dev/) or [tRPC](https://trpc.io/), in your API Worker

src/content/docs/workers/vite-plugin/vite-environments.mdx

@@ -3,7 +3,7 @@ pcx_content_type: reference
 title: Vite Environments
 head: []
 sidebar:
-  order: 4
+  order: 8
 description: Vite environments and the Vite plugin
 ---