wrangler 4.45.2 → 4.45.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wrangler",
-  "version": "4.45.2",
+  "version": "4.45.4",
   "description": "Command-line interface for all things Cloudflare Workers",
   "keywords": [
     "wrangler",
@@ -53,11 +53,11 @@
     "blake3-wasm": "2.1.5",
     "esbuild": "0.25.4",
     "path-to-regexp": "6.3.0",
-    "unenv": "2.0.0-rc.21",
+    "unenv": "2.0.0-rc.24",
     "workerd": "1.20251011.0",
     "@cloudflare/kv-asset-handler": "0.4.0",
-    "@cloudflare/unenv-preset": "2.7.8",
-    "miniflare": "4.20251011.1"
+    "@cloudflare/unenv-preset": "2.7.9",
+    "miniflare": "4.20251011.2"
   },
   "devDependencies": {
     "@aws-sdk/client-s3": "^3.721.0",
@@ -145,7 +145,7 @@
     "@cloudflare/cli": "1.1.3",
     "@cloudflare/containers-shared": "0.2.13",
     "@cloudflare/eslint-config-shared": "1.1.0",
-    "@cloudflare/pages-shared": "^0.13.81",
+    "@cloudflare/pages-shared": "^0.13.82",
     "@cloudflare/workers-shared": "0.18.8",
     "@cloudflare/workers-tsconfig": "0.0.0",
     "@cloudflare/workers-utils": "0.0.2",

package/templates/new-worker-scheduled.js

@@ -1,10 +1,10 @@
 /**
  * Welcome to Cloudflare Workers! This is your first scheduled worker.
  *
- * - Run `wrangler dev --local` in your terminal to start a development server
- * - Run `curl "http://localhost:8787/cdn-cgi/mf/scheduled"` to trigger the scheduled event
+ * - Run `wrangler dev` in your terminal to start a development server
+ * - Run `curl "http://localhost:8787/cdn-cgi/handler/scheduled"` to trigger the scheduled event
  * - Go back to the console to see what your worker has logged
- * - Update the Cron trigger in wrangler.toml (see https://developers.cloudflare.com/workers/wrangler/configuration/#triggers)
+ * - Update the Cron trigger in wrangler.toml (see https://developers.cloudflare.com/workers/configuration/cron-triggers/)
  * - Run `wrangler publish --name my-worker` to publish your worker
  *
  * Learn more at https://developers.cloudflare.com/workers/runtime-apis/scheduled-event/

package/templates/new-worker-scheduled.ts

@@ -1,10 +1,10 @@
 /**
  * Welcome to Cloudflare Workers! This is your first scheduled worker.
  *
- * - Run `wrangler dev --local` in your terminal to start a development server
- * - Run `curl "http://localhost:8787/cdn-cgi/mf/scheduled"` to trigger the scheduled event
+ * - Run `wrangler dev` in your terminal to start a development server
+ * - Run `curl "http://localhost:8787/cdn-cgi/handler/scheduled"` to trigger the scheduled event
  * - Go back to the console to see what your worker has logged
- * - Update the Cron trigger in wrangler.toml (see https://developers.cloudflare.com/workers/wrangler/configuration/#triggers)
+ * - Update the Cron trigger in wrangler.toml (see https://developers.cloudflare.com/workers/configuration/cron-triggers/)
  * - Run `wrangler deploy --name my-worker` to deploy your worker
  *
  * Learn more at https://developers.cloudflare.com/workers/runtime-apis/scheduled-event/

package/wrangler-dist/cli.d.ts

@@ -491,6 +491,9 @@ interface StartDevWorkerInput {
     };
     unsafe?: Omit<CfUnsafe, "bindings">;
     assets?: string;
+    experimental?: {
+        tailLogs: boolean;
+    };
 }
 type StartDevWorkerOptions = Omit<StartDevWorkerInput, "assets" | "containers"> & {
     /** A worker's directory. Usually where the Wrangler configuration file is located */
@@ -807,6 +810,7 @@ declare class ProxyController extends Controller<ProxyControllerEventMap> {
     runtimeMessageMutex: Mutex;
     sendMessageToProxyWorker(message: ProxyWorkerIncomingRequestBody, retries?: number): Promise<void>;
     sendMessageToInspectorProxyWorker(message: InspectorProxyWorkerIncomingWebSocketMessage, retries?: number): Promise<void>;
+    get inspectorEnabled(): boolean;
     onConfigUpdate(data: ConfigUpdateEvent): void;
     onBundleStart(data: BundleStartEvent): void;
     onReloadStart(data: ReloadStartEvent): void;
@@ -1280,7 +1284,7 @@ type CommandDefinition<NamedArgDefs extends NamedArgDefinitions = NamedArgDefini
         /**
          * If true, print a message about whether the command is operating on a local or remote resource
          */
-        printResourceLocation?: ((args?: HandlerArgs<NamedArgDefs>) => boolean) | boolean;
+        printResourceLocation?: ((args: HandlerArgs<NamedArgDefs>) => boolean) | boolean;
         /**
          * If true, check for environments in the wrangler config, if there are some and the user hasn't specified an environment
          * using the `-e|--env` cli flag, show a warning suggesting that one should instead be specified.