@cloudflare/vite-plugin 0.0.0-f6cc0293d → 0.0.0-fbba583df

package/README.md

@@ -1,6 +1,6 @@
 # `@cloudflare/vite-plugin`
 
-[Intro](#intro) | [Quick start](#quick-start) | [Tutorial](#tutorial) | [API](#api) | [Cloudflare environments](#worker-environments) | [Migrating from `wrangler dev`](#migrating-from-wrangler-dev)
+[Intro](#intro) | [Quick start](#quick-start) | [Tutorial](#tutorial) | [API](#api) | [Cloudflare environments](#cloudflare-environments) | [Migrating from `wrangler dev`](#migrating-from-wrangler-dev)
 
 ## Intro
 
@@ -16,23 +16,42 @@ Your Worker code runs inside [workerd](https://github.com/cloudflare/workerd), m
 
 ## Quick start
 
+### Start with a basic `package.json`
+
+```json
+{
+  "name": "cloudflare-vite-quick-start",
+  "private": true,
+  "version": "0.0.0",
+  "type": "module",
+  "scripts": {
+    "dev": "vite",
+    "build": "vite build",
+    "preview": "vite preview"
+  }
+}
+```
+
+> [!NOTE]
+> Ensure that you include `"type": "module"` in order to use ES modules by default.
+
 ### Install the dependencies
 
 ```sh
-npm install @cloudflare/vite-plugin wrangler --save-dev
+npm install vite @cloudflare/vite-plugin wrangler --save-dev
 ```
 
-### Add the plugin to your Vite config
+### Create your Vite config file and include the Cloudflare plugin
 
 ```ts
 // vite.config.ts
 
-import { defineConfig } from 'vite'
-import { cloudflare } from '@cloudflare/vite-plugin'
+import { defineConfig } from "vite";
+import { cloudflare } from "@cloudflare/vite-plugin";
 
 export default defineConfig({
   plugins: [cloudflare()],
-})
+});
 ```
 
 ### Create your Worker config file
@@ -40,7 +59,7 @@ export default defineConfig({
 ```toml
 # wrangler.toml
 
-name = "my-worker"
+name = "cloudflare-vite-quick-start"
 compatibility_date = "2024-12-30"
 main = "./src/index.ts"
 ```
@@ -52,12 +71,12 @@ main = "./src/index.ts"
 
 export default {
   fetch() {
-    return new Response(`Running in ${navigator.userAgent}!`)
+    return new Response(`Running in ${navigator.userAgent}!`);
   },
-}
+};
 ```
 
-You can now develop (`vite dev`), build (`vite build`), preview (`vite preview`), and deploy (`wrangler deploy`) your application.
+You can now develop (`npm run dev`), build (`npm run build`), preview (`npm run preview`), and deploy (`npm exec wrangler deploy`) your application.
 
 ## Tutorial
 
@@ -88,13 +107,13 @@ npm install @cloudflare/vite-plugin wrangler --save-dev
 ```ts
 // vite.config.ts
 
-import { defineConfig } from 'vite'
-import react from '@vitejs/plugin-react'
-import { cloudflare } from '@cloudflare/vite-plugin'
+import { defineConfig } from "vite";
+import react from "@vitejs/plugin-react";
+import { cloudflare } from "@cloudflare/vite-plugin";
 
 export default defineConfig({
   plugins: [react(), cloudflare()],
-})
+});
 ```
 
 #### Create your Worker config file
@@ -181,22 +200,22 @@ The assets `binding` defined here will allow you to access the assets functional
 // api/index.ts
 
 interface Env {
-  ASSETS: Fetcher
+  ASSETS: Fetcher;
 }
 
 export default {
   fetch(request, env) {
-    const url = new URL(request.url)
+    const url = new URL(request.url);
 
-    if (url.pathname.startsWith('/api/')) {
+    if (url.pathname.startsWith("/api/")) {
       return Response.json({
-        name: 'Cloudflare',
-      })
+        name: "Cloudflare",
+      });
     }
 
-    return env.ASSETS.fetch(request)
+    return env.ASSETS.fetch(request);
   },
-} satisfies ExportedHandler<Env>
+} satisfies ExportedHandler<Env>;
 ```
 
 The Worker above will be invoked for any request not matching a static asset.
@@ -211,14 +230,14 @@ Replace the file contents with the following code:
 ```tsx
 // src/App.tsx
 
-import { useState } from 'react'
-import reactLogo from './assets/react.svg'
-import viteLogo from '/vite.svg'
-import './App.css'
+import { useState } from "react";
+import reactLogo from "./assets/react.svg";
+import viteLogo from "/vite.svg";
+import "./App.css";
 
 function App() {
-  const [count, setCount] = useState(0)
-  const [name, setName] = useState('unknown')
+  const [count, setCount] = useState(0);
+  const [name, setName] = useState("unknown");
 
   return (
     <>
@@ -245,9 +264,9 @@ function App() {
       <div className="card">
         <button
           onClick={() => {
-            fetch('/api/')
+            fetch("/api/")
               .then((res) => res.json() as Promise<{ name: string }>)
-              .then((data) => setName(data.name))
+              .then((data) => setName(data.name));
           }}
           aria-label="get name"
         >
@@ -261,10 +280,10 @@ function App() {
         Click on the Vite and React logos to learn more
       </p>
     </>
-  )
+  );
 }
 
-export default App
+export default App;
 ```
 
 Now, if you click the button, it will display 'Name from API is: Cloudflare'.
@@ -310,12 +329,12 @@ The `cloudflare` plugin should be included in the Vite `plugins` array:
 ```ts
 // vite.config.ts
 
-import { defineConfig } from 'vite'
-import { cloudflare } from '@cloudflare/vite-plugin'
+import { defineConfig } from "vite";
+import { cloudflare } from "@cloudflare/vite-plugin";
 
 export default defineConfig({
   plugins: [cloudflare()],
-})
+});
 ```
 
 It accepts an optional `PluginConfig` parameter.
@@ -447,6 +466,13 @@ The value of `MY_VAR` will therefore be `'Production var'`.
 If you run `vite build --mode staging` then the 'staging' Vite mode will be used and the 'staging' Cloudflare environment will be selected.
 The value of `MY_VAR` will therefore be `'Staging var'`.
 
+## Secrets
+
+Secrets can be provided to your Worker in local development using a [`.dev.vars`](https://developers.cloudflare.com/workers/configuration/secrets/#local-development-with-secrets) file. If you are using [Cloudflare Environments](#cloudflare-environments) then the relevant `.dev.vars` file will be selected. For example, `CLOUDFLARE_ENV=staging vite dev` will load `.dev.vars.staging` if it exists and fall back to `.dev.vars`.
+
+> [!NOTE]
+> The `vite build` command copies the relevant `.dev.vars[.env-name]` file to the output directory. This is only used when running `vite preview` and is not deployed with your Worker.
+
 ## Migrating from `wrangler dev`
 
 Migrating from `wrangler dev` is a simple process and you can follow the instructions in the [Quick start](#quick-start) to get started.