Update Vite plugin static assets page

Author: jamesopstad

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

@@ -8,14 +8,17 @@ description: Static assets and the Vite plugin
 
 import { WranglerConfig } from "~/components";
 
-The Vite plugin does not require that you provide the `assets` field in order to enable assets and instead determines whether assets should be included based on whether the `client` environment has been built.
-By default, the `client` environment is built if there is an `index.html` file in the root of your project or if `build.rollupOptions.input` is specified in the Vite config.
+This guide focuses on the areas of working with static assets that are unique to the Vite plugin.
+For more general documentation, see [Static Assets](/workers/static-assets/).
 
-:::note
-When using the Cloudflare Vite plugin, the `client` environment is deployed as your static assets.
-This typically includes files such as static HTML, front-end JavaScript, CSS, images and fonts.
-For more information about using static assets in Vite, refer to [Static Asset Handling](https://vite.dev/guide/assets).
-:::
+## Configuration
+
+The Vite plugin does not require that you provide the `assets` field in order to enable assets and instead determines whether assets should be included based on whether the `client` environment has been built. By default, the `client` environment is built if any of the following conditions are met:
+
+- There is an `index.html` file in the root of your project
+- `build.rollupOptions.input` or `environments.client.build.rollupOptions.input` is specified in your Vite config
+- You have a non-empty [`public` directory](https://vite.dev/guide/assets#the-public-directory)
+- Your entry Worker [imports assets as URLs](https://vite.dev/guide/assets#importing-asset-as-url)
 
 On running `vite build`, an output `wrangler.json` configuration file is generated as part of the build output.
 The `assets.directory` field in this file is automatically populated with the path to your `client` build output.
@@ -32,10 +35,34 @@ assets = { not_found_handling = "single-page-application" }
 
 </WranglerConfig>
 
+## Features
+
+The Vite plugin ensures that all of Vite's [static asset handling](https://vite.dev/guide/assets) features are supported in your Worker as well as in your frontend.
+This includes importing assets as URLs, inlining assets, importing assets as strings and importing assets from the `public` directory.
+
+Assets [imported as URLs](https://vite.dev/guide/assets#importing-asset-as-url) can be fetched via the [assets binding](/workers/static-assets/binding/#binding).
+As the binding's `fetch` method requires a full URL, we recommend using the request URL as the `base`.
+This is demonstrated in the following example:
+
+```ts
+import assetPath from "./my-image.svg";
+
+export default {
+	async fetch(request, env) {
+		return env.ASSETS.fetch(new URL(assetPath, request.url));
+	},
+};
+```
+
+Assets imported as URLs in your Worker will automatically be moved from the Worker to the client build output.
+When running `vite build` the paths of any moved assets will be displayed in the console.
+
+:::note
+If you are developing a multi-Worker application, assets can only be accessed on the client and in your entry Worker.
+:::
+
 ## Headers and redirects
 
 Custom [headers](/workers/static-assets/headers/) and [redirects](/workers/static-assets/redirects/) are supported at build, preview and deploy time by adding `_headers` and `_redirects` files to your [`public` directory](https://vite.dev/guide/assets#the-public-directory).
 The paths in these files should reflect the structure of your client build output.
 For example, generated assets are typically located in an [assets subdirectory](https://vite.dev/config/build-options#build-assetsdir).
-
-<br />