Update compatibility dates

Author: jamesopstad

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

@@ -17,7 +17,7 @@ Consider the following example Worker config file:
 
 ```toml
 name = "my-worker"
-compatibility_date = "2024-12-30"
+compatibility_date = "2025-04-03"
 main = "./src/index.ts"
 
 vars = { MY_VAR = "Top-level var" }
@@ -36,7 +36,7 @@ If you run `CLOUDFLARE_ENV=production vite build` then the output `wrangler.json
 ```json
 {
 	"name": "my-worker",
-	"compatibility_date": "2024-12-30",
+	"compatibility_date": "2025-04-03",
 	"main": "index.js",
 	"vars": { "MY_VAR": "Production var" }
 }
@@ -72,7 +72,7 @@ Consider again the previous example:
 # wrangler.toml
 
 name = "my-worker"
-compatibility_date = "2024-12-30"
+compatibility_date = "2025-04-03"
 main = "./src/index.ts"
 
 vars = { MY_VAR = "Top-level var" }

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

@@ -62,7 +62,7 @@ Refer to the [API reference](/workers/vite-plugin/api/) for configuration option
 
 ```toml
 name = "cloudflare-vite-quick-start"
-compatibility_date = "2024-12-30"
+compatibility_date = "2025-04-03"
 main = "./src/index.ts"
 ```
 

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

@@ -61,7 +61,7 @@ export default defineConfig({
 
 ```toml
 name = "cloudflare-vite-tutorial"
-compatibility_date = "2024-12-30"
+compatibility_date = "2025-04-03"
 assets = { not_found_handling = "single-page-application" }
 ```
 
@@ -138,7 +138,7 @@ This tutorial, however, will show you how to go a step further and add an API Wo
 
 ```toml
 name = "cloudflare-vite-tutorial"
-compatibility_date = "2024-12-30"
+compatibility_date = "2025-04-03"
 assets = { not_found_handling = "single-page-application" }
 main = "./worker/index.ts"
 ```

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

@@ -35,7 +35,7 @@ We use the Vite config to set global constant replacements for this environment:
 
 ```toml
 name = "my-worker"
-compatibility_date = "2024-12-30"
+compatibility_date = "2025-04-03"
 main = "./src/index.ts"
 ```