@dragonmastery/tamer 0.1.0 → 0.1.2

package/dist/index.d.mts

@@ -1,80 +1,2345 @@
-//#region src/generated/wrangler-types.d.ts
+//#region src/generated/wrangler-types.generated.d.ts
+/**
+ * Auto-generated from wrangler JSON schema.
+ * Do not edit manually. Run: bun run generate:wrangler-types
+ */
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "Route".
+ */
+type Route = string | ZoneIdRoute | ZoneNameRoute | CustomDomainRoute;
 /**
- * TypeScript types for Cloudflare Wrangler configuration.
- * Hand-written to match wrangler config-schema.json (workers-utils is no longer on npm).
+ * The possible types for a `Rule`.
  *
- * Generated from: node_modules/wrangler/config-schema.json
- * See: https://developers.cloudflare.com/workers/wrangler/configuration/
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "ConfigModuleRuleType".
+ */
+type ConfigModuleRuleType = "ESModule" | "CommonJS" | "CompiledWasm" | "Text" | "Data" | "PythonModule" | "PythonRequirement";
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "Json".
+ */
+type Json = string | number | boolean | null | Json[] | {
+  [k: string]: Json;
+};
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "DurableObjectBindings".
+ */
+type DurableObjectBindings = {
+  /**
+   * The name of the binding used to refer to the Durable Object
+   */
+  name: string;
+  /**
+   * The exported class name of the Durable Object
+   */
+  class_name: string;
+  /**
+   * The script where the Durable Object is defined (if it's external to this Worker)
+   */
+  script_name?: string;
+  /**
+   * The service environment of the script_name to bind to
+   */
+  environment?: string;
+}[];
+/**
+ * The raw environment configuration that we read from the config file.
+ *
+ * All the properties are optional, and will be replaced with defaults in the configuration that is used in the rest of the codebase.
+ *
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "RawEnvironment".
  */
-/** D1 database binding in wrangler config */
-interface WranglerD1Database {
-  binding: string;
-  database_id?: string;
-  database_name?: string;
-  database_internal_env?: string;
-  migrations_dir?: string;
-  migrations_table?: string;
-  preview_database_id?: string;
-}
-/** R2 bucket binding in wrangler config */
-interface WranglerR2Bucket {
-  binding: string;
-  bucket_name?: string;
-  jurisdiction?: string;
-}
-/** KV namespace binding in wrangler config */
-interface WranglerKVNamespace {
-  binding: string;
-  id?: string;
-  preview_id?: string;
-}
-/** Raw environment block (default or named env in wrangler config) */
 interface RawEnvironment {
+  /**
+   * The name of your Worker. Alphanumeric + dashes only.
+   */
   name?: string;
+  /**
+   * This is the ID of the account associated with your zone. You might have more than one account, so make sure to use the ID of the account associated with the zone/route you provide, if you provide one. It can also be specified through the CLOUDFLARE_ACCOUNT_ID environment variable.
+   */
   account_id?: string;
+  /**
+   * A date in the form yyyy-mm-dd, which will be used to determine which version of the Workers runtime is used.
+   *
+   * More details at https://developers.cloudflare.com/workers/configuration/compatibility-dates
+   */
   compatibility_date?: string;
+  /**
+   * A list of flags that enable features from upcoming features of the Workers runtime, usually used together with compatibility_date.
+   *
+   * More details at https://developers.cloudflare.com/workers/configuration/compatibility-flags/
+   */
   compatibility_flags?: string[];
-  d1_databases?: WranglerD1Database[];
-  r2_buckets?: WranglerR2Bucket[];
-  kv_namespaces?: WranglerKVNamespace[];
-  vars?: Record<string, string>;
-  routes?: Array<{
-    pattern: string;
-    zone_name?: string;
-    custom_domain?: boolean;
-  }>;
-  route?: string;
-  [key: string]: unknown;
+  /**
+   * The entrypoint/path to the JavaScript file that will be executed.
+   */
+  main?: string;
+  /**
+   * If true then Wrangler will traverse the file tree below `base_dir`; Any files that match `rules` will be included in the deployed Worker. Defaults to true if `no_bundle` is true, otherwise false.
+   */
+  find_additional_modules?: boolean;
+  /**
+   * Determines whether Wrangler will preserve bundled file names. Defaults to false. If left unset, files will be named using the pattern ${fileHash}-${basename}, for example, `34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico`.
+   */
+  preserve_file_names?: boolean;
+  /**
+   * The directory in which module rules should be evaluated when including additional files into a Worker deployment. This defaults to the directory containing the `main` entry point of the Worker if not specified.
+   */
+  base_dir?: string;
+  /**
+   * Whether we use <name>.<subdomain>.workers.dev to test and deploy your Worker.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workersdev
+   */
+  workers_dev?: boolean;
+  /**
+   * Whether we use <version>-<name>.<subdomain>.workers.dev to serve Preview URLs for your Worker.
+   */
+  preview_urls?: boolean;
+  /**
+   * A list of routes that your Worker should be published to. Only one of `routes` or `route` is required.
+   *
+   * Only required when workers_dev is false, and there's no scheduled Worker (see `triggers`)
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#types-of-routes
+   */
+  routes?: Route[];
+  /**
+   * A route that your Worker should be published to. Literally the same as routes, but only one. Only one of `routes` or `route` is required.
+   *
+   * Only required when workers_dev is false, and there's no scheduled Worker
+   */
+  route?: string | ZoneIdRoute | ZoneNameRoute | CustomDomainRoute;
+  /**
+   * Path to a custom tsconfig
+   */
+  tsconfig?: string;
+  /**
+   * The function to use to replace jsx syntax.
+   */
+  jsx_factory?: string;
+  /**
+   * The function to use to replace jsx fragment syntax.
+   */
+  jsx_fragment?: string;
+  /**
+   * A list of migrations that should be uploaded with your Worker.
+   *
+   * These define changes in your Durable Object declarations.
+   *
+   * More details at https://developers.cloudflare.com/workers/learning/using-durable-objects#configuring-durable-object-classes-with-migrations
+   */
+  migrations?: DurableObjectMigration[];
+  /**
+   * "Cron" definitions to trigger a Worker's "scheduled" function.
+   *
+   * Lets you call Workers periodically, much like a cron job.
+   *
+   * More details here https://developers.cloudflare.com/workers/platform/cron-triggers
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#triggers
+   */
+  triggers?: {
+    crons?: string[];
+  };
+  /**
+   * Specify limits for runtime behavior. Only supported for the "standard" Usage Model
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#limits
+   */
+  limits?: {
+    /**
+     * Maximum allowed CPU time for a Worker's invocation in milliseconds
+     */
+    cpu_ms?: number;
+    /**
+     * Maximum allowed number of fetch requests that a Worker's invocation can execute
+     */
+    subrequests?: number;
+  };
+  /**
+   * An ordered list of rules that define which modules to import, and what type to import them as. You will need to specify rules to use Text, Data, and CompiledWasm modules, or when you wish to have a .js file be treated as an ESModule instead of CommonJS.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#bundling
+   */
+  rules?: Rule[];
+  /**
+   * Configures a custom build step to be run by Wrangler when building your Worker.
+   *
+   * Refer to the [custom builds documentation](https://developers.cloudflare.com/workers/cli-wrangler/configuration#build) for more details.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#custom-builds
+   */
+  build?: {
+    /**
+     * The command used to build your Worker. On Linux and macOS, the command is executed in the `sh` shell and the `cmd` shell for Windows. The `&&` and `||` shell operators may be used.
+     */
+    command?: string;
+    /**
+     * The directory in which the command is executed.
+     */
+    cwd?: string;
+    /**
+     * The directory to watch for changes while using wrangler dev, defaults to the current working directory
+     */
+    watch_dir?: string | string[];
+  };
+  /**
+   * Skip internal build steps and directly deploy script
+   */
+  no_bundle?: boolean;
+  /**
+   * Minify the script before uploading.
+   */
+  minify?: boolean;
+  /**
+   * Set the `name` property to the original name for functions and classes renamed during minification.
+   *
+   * See https://esbuild.github.io/api/#keep-names
+   */
+  keep_names?: boolean;
+  /**
+   * Designates this Worker as an internal-only "first-party" Worker.
+   */
+  first_party_worker?: boolean;
+  /**
+   * List of bindings that you will send to logfwdr
+   */
+  logfwdr?: {
+    bindings: {
+      /**
+       * The binding name used to refer to logfwdr
+       */
+      name: string;
+      /**
+       * The destination for this logged message
+       */
+      destination: string;
+    }[];
+  };
+  /**
+   * Send Trace Events from this Worker to Workers Logpush.
+   *
+   * This will not configure a corresponding Logpush job automatically.
+   *
+   * For more information about Workers Logpush, see: https://blog.cloudflare.com/logpush-for-workers/
+   */
+  logpush?: boolean;
+  /**
+   * Include source maps when uploading this worker.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#source-maps
+   */
+  upload_source_maps?: boolean;
+  /**
+   * Specify how the Worker should be located to minimize round-trip time.
+   *
+   * More details: https://developers.cloudflare.com/workers/platform/smart-placement/
+   */
+  placement?: {
+    mode: "off" | "smart";
+    hint?: string;
+  } | {
+    mode?: "targeted";
+    region: string;
+  } | {
+    mode?: "targeted";
+    host: string;
+  } | {
+    mode?: "targeted";
+    hostname: string;
+  };
+  /**
+   * Specify the directory of static assets to deploy/serve
+   *
+   * More details at https://developers.cloudflare.com/workers/frameworks/
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#assets
+   */
+  assets?: {
+    /**
+     * Absolute path to assets directory
+     */
+    directory?: string;
+    /**
+     * Name of `env` binding property in the User Worker.
+     */
+    binding?: string;
+    /**
+     * How to handle HTML requests.
+     */
+    html_handling?: "auto-trailing-slash" | "force-trailing-slash" | "drop-trailing-slash" | "none";
+    /**
+     * How to handle requests that do not match an asset.
+     */
+    not_found_handling?: "single-page-application" | "404-page" | "none";
+    /**
+     * Matches will be routed to the User Worker, and matches to negative rules will go to the Asset Worker.
+     *
+     * Can also be `true`, indicating that every request should be routed to the User Worker.
+     */
+    run_worker_first?: string[] | boolean;
+  };
+  /**
+   * Specify the observability behavior of the Worker.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#observability
+   */
+  observability?: {
+    /**
+     * If observability is enabled for this Worker
+     */
+    enabled?: boolean;
+    /**
+     * The sampling rate
+     */
+    head_sampling_rate?: number;
+    logs?: {
+      enabled?: boolean;
+      /**
+       * The sampling rate
+       */
+      head_sampling_rate?: number;
+      /**
+       * Set to false to disable invocation logs
+       */
+      invocation_logs?: boolean;
+      /**
+       * If logs should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
+       */
+      persist?: boolean;
+      /**
+       * What destinations logs emitted from the Worker should be sent to.
+       */
+      destinations?: string[];
+    };
+    traces?: {
+      enabled?: boolean;
+      /**
+       * The sampling rate
+       */
+      head_sampling_rate?: number;
+      /**
+       * If traces should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
+       */
+      persist?: boolean;
+      /**
+       * What destinations traces emitted from the Worker should be sent to.
+       */
+      destinations?: string[];
+    };
+  };
+  /**
+   * Specify the compliance region mode of the Worker.
+   *
+   * Although if the user does not specify a compliance region, the default is `public`, it can be set to `undefined` in configuration to delegate to the CLOUDFLARE_COMPLIANCE_REGION environment variable.
+   */
+  compliance_region?: "public" | "fedramp_high";
+  /**
+   * Configuration for Python modules.
+   */
+  python_modules?: {
+    /**
+     * A list of glob patterns to exclude files from the python_modules directory when bundling.
+     *
+     * Patterns are relative to the python_modules directory and use glob syntax.
+     */
+    exclude: string[];
+  };
+  /**
+   * A map of values to substitute when deploying your Worker.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  define?: {
+    [k: string]: string;
+  };
+  /**
+   * A map of environment variables to set when deploying your Worker.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
+   */
+  vars?: {
+    [k: string]: string | Json;
+  };
+  /**
+   * Secrets configuration (experimental).
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  secrets?: {
+    /**
+     * List of secret names that are required by your Worker. When defined, this property:
+     * - Replaces .dev.vars/.env/process.env inference for type generation
+     * - Enables local dev validation with warnings for missing secrets
+     */
+    required?: string[];
+  };
+  /**
+   * A list of durable objects that your Worker should be bound to.
+   *
+   * For more information about Durable Objects, see the documentation at https://developers.cloudflare.com/workers/learning/using-durable-objects
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#durable-objects
+   */
+  durable_objects?: {
+    bindings: DurableObjectBindings;
+  };
+  /**
+   * A list of workflows that your Worker should be bound to.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  workflows?: WorkflowBinding[];
+  /**
+   * Cloudchamber configuration
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  cloudchamber?: {
+    image?: string;
+    location?: string;
+    instance_type?: "dev" | "basic" | "standard" | "lite" | "standard-1" | "standard-2" | "standard-3" | "standard-4";
+    vcpu?: number;
+    memory?: string;
+    ipv4?: boolean;
+  };
+  /**
+   * Container related configuration
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  containers?: ContainerApp[];
+  /**
+   * These specify any Workers KV Namespaces you want to access from inside your Worker.
+   *
+   * To learn more about KV Namespaces, see the documentation at https://developers.cloudflare.com/workers/learning/how-kv-works
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#kv-namespaces
+   */
+  kv_namespaces?: {
+    /**
+     * The binding name used to refer to the KV Namespace
+     */
+    binding: string;
+    /**
+     * The ID of the KV namespace
+     */
+    id?: string;
+    /**
+     * The ID of the KV namespace used during `wrangler dev`
+     */
+    preview_id?: string;
+    /**
+     * Whether the KV namespace should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * These specify bindings to send email from inside your Worker.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#email-bindings
+   */
+  send_email?: {
+    /**
+     * The binding name used to refer to the this binding
+     */
+    name: string;
+    /**
+     * If this binding should be restricted to a specific verified address
+     */
+    destination_address?: string;
+    /**
+     * If this binding should be restricted to a set of verified addresses
+     */
+    allowed_destination_addresses?: string[];
+    /**
+     * If this binding should be restricted to a set of sender addresses
+     */
+    allowed_sender_addresses?: string[];
+    /**
+     * Whether the binding should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies Queues that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#queues
+   */
+  queues?: {
+    /**
+     * Producer bindings
+     */
+    producers?: {
+      /**
+       * The binding name used to refer to the Queue in the Worker.
+       */
+      binding: string;
+      /**
+       * The name of this Queue.
+       */
+      queue: string;
+      /**
+       * The number of seconds to wait before delivering a message
+       */
+      delivery_delay?: number;
+      /**
+       * Whether the Queue producer should be remote or not in local development
+       */
+      remote?: boolean;
+    }[];
+    /**
+     * Consumer configuration
+     */
+    consumers?: {
+      /**
+       * The name of the queue from which this consumer should consume.
+       */
+      queue: string;
+      /**
+       * The consumer type, e.g., worker, http-pull, r2-bucket, etc. Default is worker.
+       */
+      type?: string;
+      /**
+       * The maximum number of messages per batch
+       */
+      max_batch_size?: number;
+      /**
+       * The maximum number of seconds to wait to fill a batch with messages.
+       */
+      max_batch_timeout?: number;
+      /**
+       * The maximum number of retries for each message.
+       */
+      max_retries?: number;
+      /**
+       * The queue to send messages that failed to be consumed.
+       */
+      dead_letter_queue?: string;
+      /**
+       * The maximum number of concurrent consumer Worker invocations. Leaving this unset will allow your consumer to scale to the maximum concurrency needed to keep up with the message backlog.
+       */
+      max_concurrency?: number | null;
+      /**
+       * The number of milliseconds to wait for pulled messages to become visible again
+       */
+      visibility_timeout_ms?: number;
+      /**
+       * The number of seconds to wait before retrying a message
+       */
+      retry_delay?: number;
+    }[];
+  };
+  /**
+   * Specifies R2 buckets that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#r2-buckets
+   */
+  r2_buckets?: {
+    /**
+     * The binding name used to refer to the R2 bucket in the Worker.
+     */
+    binding: string;
+    /**
+     * The name of this R2 bucket at the edge.
+     */
+    bucket_name?: string;
+    /**
+     * The preview name of this R2 bucket at the edge.
+     */
+    preview_bucket_name?: string;
+    /**
+     * The jurisdiction that the bucket exists in. Default if not present.
+     */
+    jurisdiction?: string;
+    /**
+     * Whether the R2 bucket should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies D1 databases that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#d1-databases
+   */
+  d1_databases?: {
+    /**
+     * The binding name used to refer to the D1 database in the Worker.
+     */
+    binding: string;
+    /**
+     * The name of this D1 database.
+     */
+    database_name?: string;
+    /**
+     * The UUID of this D1 database (not required).
+     */
+    database_id?: string;
+    /**
+     * The UUID of this D1 database for Wrangler Dev (if specified).
+     */
+    preview_database_id?: string;
+    /**
+     * The name of the migrations table for this D1 database (defaults to 'd1_migrations').
+     */
+    migrations_table?: string;
+    /**
+     * The path to the directory of migrations for this D1 database (defaults to './migrations').
+     */
+    migrations_dir?: string;
+    /**
+     * Internal use only.
+     */
+    database_internal_env?: string;
+    /**
+     * Whether the D1 database should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies Vectorize indexes that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#vectorize-indexes
+   */
+  vectorize?: {
+    /**
+     * The binding name used to refer to the Vectorize index in the Worker.
+     */
+    binding: string;
+    /**
+     * The name of the index.
+     */
+    index_name: string;
+    /**
+     * Whether the Vectorize index should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies Hyperdrive configs that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#hyperdrive
+   */
+  hyperdrive?: {
+    /**
+     * The binding name used to refer to the project in the Worker.
+     */
+    binding: string;
+    /**
+     * The id of the database.
+     */
+    id: string;
+    /**
+     * The local database connection string for `wrangler dev`
+     */
+    localConnectionString?: string;
+  }[];
+  /**
+   * Specifies service bindings (Worker-to-Worker) that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#service-bindings
+   */
+  services?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * The name of the service. To bind to a worker in a specific environment, you should use the format `<worker_name>-<environment_name>`.
+     */
+    service: string;
+    /**
+     * Optionally, the entrypoint (named export) of the service to bind to.
+     */
+    entrypoint?: string;
+    /**
+     * Optional properties that will be made available to the service via ctx.props.
+     */
+    props?: {
+      [k: string]: unknown;
+    };
+    /**
+     * Whether the service binding should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies analytics engine datasets that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#analytics-engine-datasets
+   */
+  analytics_engine_datasets?: {
+    /**
+     * The binding name used to refer to the dataset in the Worker.
+     */
+    binding: string;
+    /**
+     * The name of this dataset to write to.
+     */
+    dataset?: string;
+  }[];
+  /**
+   * A browser that will be usable from the Worker.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#browser-rendering
+   */
+  browser?: {
+    binding: string;
+    /**
+     * Whether the Browser binding should be remote or not in local development
+     */
+    remote?: boolean;
+  };
+  /**
+   * Binding to the AI project.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workers-ai
+   */
+  ai?: {
+    binding: string;
+    staging?: boolean;
+    /**
+     * Whether the AI binding should be remote or not in local development
+     */
+    remote?: boolean;
+  };
+  /**
+   * Binding to Cloudflare Images
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#images
+   */
+  images?: {
+    binding: string;
+    /**
+     * Whether the Images binding should be remote or not in local development
+     */
+    remote?: boolean;
+  };
+  /**
+   * Binding to Cloudflare Media Transformations
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  media?: {
+    binding: string;
+    /**
+     * Whether the Media binding should be remote or not
+     */
+    remote?: boolean;
+  };
+  /**
+   * Binding to the Worker Version's metadata
+   */
+  version_metadata?: {
+    binding: string;
+  };
+  /**
+   * "Unsafe" tables for features that aren't directly supported by wrangler.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  unsafe?: {
+    /**
+     * A set of bindings that should be put into a Worker's upload metadata without changes. These can be used to implement bindings for features that haven't released and aren't supported directly by wrangler or miniflare.
+     */
+    bindings?: {
+      /**
+       * The name of the binding provided to the Worker
+       */
+      name: string;
+      /**
+       * The 'type' of the unsafe binding.
+       */
+      type: string;
+      dev?: {
+        plugin: {
+          /**
+           * Package is the bare specifier of the package that exposes plugins to integrate into Miniflare via a named `plugins` export.
+           */
+          package: string;
+          /**
+           * Plugin is the name of the plugin exposed by the package.
+           */
+          name: string;
+        };
+        /**
+         * Optional mapping of unsafe bindings names to options provided for the plugin.
+         */
+        options?: {
+          [k: string]: unknown;
+        };
+      };
+      [k: string]: unknown;
+    }[];
+    /**
+     * Arbitrary key/value pairs that will be included in the uploaded metadata.  Values specified here will always be applied to metadata last, so can add new or override existing fields.
+     */
+    metadata?: {
+      [k: string]: unknown;
+    };
+    /**
+     * Used for internal capnp uploads for the Workers runtime
+     */
+    capnp?: {
+      base_path: string;
+      source_schemas: string[];
+    } | {
+      compiled_schema: string;
+    };
+  };
+  /**
+   * Specifies a list of mTLS certificates that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#mtls-certificates
+   */
+  mtls_certificates?: {
+    /**
+     * The binding name used to refer to the certificate in the Worker
+     */
+    binding: string;
+    /**
+     * The uuid of the uploaded mTLS certificate
+     */
+    certificate_id: string;
+    /**
+     * Whether the mtls fetcher should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies a list of Tail Workers that are bound to this Worker environment
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  tail_consumers?: TailConsumer[];
+  /**
+   * Specifies a list of Streaming Tail Workers that are bound to this Worker environment
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  streaming_tail_consumers?: StreamingTailConsumer[];
+  /**
+   * Specifies namespace bindings that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#dispatch-namespace-bindings-workers-for-platforms
+   */
+  dispatch_namespaces?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * The namespace to bind to.
+     */
+    namespace: string;
+    /**
+     * Details about the outbound Worker which will handle outbound requests from your namespace
+     */
+    outbound?: {
+      /**
+       * Name of the service handling the outbound requests
+       */
+      service: string;
+      /**
+       * (Optional) Name of the environment handling the outbound requests.
+       */
+      environment?: string;
+      /**
+       * (Optional) List of parameter names, for sending context from your dispatch Worker to the outbound handler
+       */
+      parameters?: string[];
+    };
+    /**
+     * Whether the Dispatch Namespace should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies list of Pipelines bound to this Worker environment
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  pipelines?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * Name of the Pipeline to bind
+     */
+    pipeline: string;
+    /**
+     * Whether the pipeline should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies Secret Store bindings that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  secrets_store_secrets?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * Id of the secret store
+     */
+    store_id: string;
+    /**
+     * Name of the secret
+     */
+    secret_name: string;
+  }[];
+  /**
+   * **DO NOT USE**. Hello World Binding Config to serve as an explanatory example.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  unsafe_hello_world?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * Whether the timer is enabled
+     */
+    enable_timer?: boolean;
+  }[];
+  /**
+   * Specifies rate limit bindings that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  ratelimits?: {
+    /**
+     * The binding name used to refer to the rate limiter in the Worker.
+     */
+    name: string;
+    /**
+     * The namespace ID for this rate limiter.
+     */
+    namespace_id: string;
+    /**
+     * Simple rate limiting configuration.
+     */
+    simple: {
+      /**
+       * The maximum number of requests allowed in the time period.
+       */
+      limit: number;
+      /**
+       * The time period in seconds (10 for ten seconds, 60 for one minute).
+       */
+      period: 10 | 60;
+    };
+  }[];
+  /**
+   * Specifies Worker Loader bindings that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  worker_loaders?: {
+    /**
+     * The binding name used to refer to the Worker Loader in the Worker.
+     */
+    binding: string;
+  }[];
+  /**
+   * Specifies VPC services that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  vpc_services?: {
+    /**
+     * The binding name used to refer to the VPC service in the Worker.
+     */
+    binding: string;
+    /**
+     * The service ID of the VPC connectivity service.
+     */
+    service_id: string;
+    /**
+     * Whether the VPC service is remote or not
+     */
+    remote?: boolean;
+  }[];
+}
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "ZoneIdRoute".
+ */
+interface ZoneIdRoute {
+  pattern: string;
+  zone_id: string;
+  custom_domain?: boolean;
+}
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "ZoneNameRoute".
+ */
+interface ZoneNameRoute {
+  pattern: string;
+  zone_name: string;
+  custom_domain?: boolean;
+}
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "CustomDomainRoute".
+ */
+interface CustomDomainRoute {
+  pattern: string;
+  custom_domain: boolean;
 }
-/** Full wrangler config (root of wrangler.json / wrangler.toml) */
+/**
+ * Configuration in wrangler for Durable Object Migrations
+ *
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "DurableObjectMigration".
+ */
+interface DurableObjectMigration {
+  /**
+   * A unique identifier for this migration.
+   */
+  tag: string;
+  /**
+   * The new Durable Objects being defined.
+   */
+  new_classes?: string[];
+  /**
+   * The new SQLite Durable Objects being defined.
+   */
+  new_sqlite_classes?: string[];
+  /**
+   * The Durable Objects being renamed.
+   */
+  renamed_classes?: {
+    from: string;
+    to: string;
+  }[];
+  /**
+   * The Durable Objects being removed.
+   */
+  deleted_classes?: string[];
+}
+/**
+ * A bundling resolver rule, defining the modules type for paths that match the specified globs.
+ *
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "Rule".
+ */
+interface Rule {
+  type: ConfigModuleRuleType;
+  globs: string[];
+  fallthrough?: boolean;
+}
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "WorkflowBinding".
+ */
+interface WorkflowBinding {
+  /**
+   * The name of the binding used to refer to the Workflow
+   */
+  binding: string;
+  /**
+   * The name of the Workflow
+   */
+  name: string;
+  /**
+   * The exported class name of the Workflow
+   */
+  class_name: string;
+  /**
+   * The script where the Workflow is defined (if it's external to this Worker)
+   */
+  script_name?: string;
+  /**
+   * Whether the Workflow should be remote or not in local development
+   */
+  remote?: boolean;
+  /**
+   * Optional limits for the Workflow
+   */
+  limits?: {
+    /**
+     * Maximum number of steps a Workflow instance can execute
+     */
+    steps?: number;
+  };
+}
+/**
+ * Configuration for a container application
+ *
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "ContainerApp".
+ */
+interface ContainerApp {
+  /**
+   * Name of the application
+   */
+  name?: string;
+  /**
+   * Number of maximum application instances.
+   */
+  max_instances?: number;
+  /**
+   * The path to a Dockerfile, or an image URI for the Cloudflare registry.
+   */
+  image: string;
+  /**
+   * Build context of the application.
+   */
+  image_build_context?: string;
+  /**
+   * Image variables available to the image at build-time only. For runtime env vars, refer to https://developers.cloudflare.com/containers/examples/env-vars-and-secrets/
+   */
+  image_vars?: {
+    [k: string]: string;
+  };
+  /**
+   * The class name of the Durable Object the container is connected to.
+   */
+  class_name: string;
+  /**
+   * The scheduling policy of the application
+   */
+  scheduling_policy?: "default" | "moon" | "regional";
+  /**
+   * The instance type to be used for the container. Select from one of the following named instance types:  - lite: 1/16 vCPU, 256 MiB memory, and 2 GB disk  - basic: 1/4 vCPU, 1 GiB memory, and 4 GB disk  - standard-1: 1/2 vCPU, 4 GiB memory, and 8 GB disk  - standard-2: 1 vCPU, 6 GiB memory, and 12 GB disk  - standard-3: 2 vCPU, 8 GiB memory, and 16 GB disk  - standard-4: 4 vCPU, 12 GiB memory, and 20 GB disk  - dev: 1/16 vCPU, 256 MiB memory, and 2 GB disk (deprecated, use "lite" instead)  - standard: 1 vCPU, 4 GiB memory, and 4 GB disk (deprecated, use "standard-1" instead)
+   *
+   * Customers on an enterprise plan have the additional option to set custom limits.
+   */
+  instance_type?: "dev" | "basic" | "standard" | "lite" | "standard-1" | "standard-2" | "standard-3" | "standard-4" | {
+    vcpu?: number;
+    memory_mib?: number;
+    disk_mb?: number;
+  };
+  wrangler_ssh?: {
+    /**
+     * If enabled, those with write access to a container will be able to SSH into it through Wrangler.
+     */
+    enabled: boolean;
+    /**
+     * Port that the SSH service is running on
+     */
+    port?: number;
+  };
+  /**
+   * SSH public keys to put in the container's authorized_keys file.
+   */
+  authorized_keys?: {
+    name: string;
+    public_key: string;
+  }[];
+  /**
+   * Trusted user CA keys to put in the container's trusted_user_ca_keys file.
+   */
+  trusted_user_ca_keys?: {
+    name?: string;
+    public_key: string;
+  }[];
+  /**
+   * Configures what percentage of instances should be updated at each step of a rollout. You can specify this as a single number, or an array of numbers.
+   *
+   * If this is a single number, each step will progress by that percentage. The options are 5, 10, 20, 25, 50 or 100.
+   *
+   * If this is an array, each step specifies the cumulative rollout progress. The final step must be 100.
+   *
+   * This can be overridden adhoc by deploying with the `--containers-rollout=immediate` flag, which will roll out to 100% of instances in one step.
+   */
+  rollout_step_percentage?: number | number[];
+  /**
+   * Configures the grace period (in seconds) for active instances before being shutdown during a rollout.
+   */
+  rollout_active_grace_period?: number;
+}
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "TailConsumer".
+ */
+interface TailConsumer {
+  /**
+   * The name of the service tail events will be forwarded to.
+   */
+  service: string;
+  /**
+   * (Optional) The environment of the service.
+   */
+  environment?: string;
+}
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "StreamingTailConsumer".
+ */
+interface StreamingTailConsumer {
+  /**
+   * The name of the service streaming tail events will be forwarded to.
+   */
+  service: string;
+}
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "DockerConfiguration".
+ */
+interface DockerConfiguration {
+  /**
+   * Socket used by miniflare to communicate with Docker
+   */
+  socketPath: string;
+  /**
+   * Docker image name for the container egress interceptor sidecar
+   */
+  containerEgressInterceptorImage?: string;
+}
+/**
+ * This interface was referenced by `WranglerSchema`'s JSON-Schema
+ * via the `definition` "RawConfig".
+ */
 interface RawConfig {
   $schema?: string;
+  /**
+   * The `env` section defines overrides for the configuration for different environments.
+   *
+   * All environment fields can be specified at the top level of the config indicating the default environment settings.
+   *
+   * - Some fields are inherited and overridable in each environment.
+   * - But some are not inherited and must be explicitly specified in every environment, if they are specified at the top level.
+   *
+   * For more information, see the documentation at https://developers.cloudflare.com/workers/cli-wrangler/configuration#environments
+   */
+  env?: {
+    [k: string]: RawEnvironment;
+  };
+  /**
+   * The name of your Worker. Alphanumeric + dashes only.
+   */
   name?: string;
-  main?: string;
+  /**
+   * This is the ID of the account associated with your zone. You might have more than one account, so make sure to use the ID of the account associated with the zone/route you provide, if you provide one. It can also be specified through the CLOUDFLARE_ACCOUNT_ID environment variable.
+   */
   account_id?: string;
+  /**
+   * A date in the form yyyy-mm-dd, which will be used to determine which version of the Workers runtime is used.
+   *
+   * More details at https://developers.cloudflare.com/workers/configuration/compatibility-dates
+   */
   compatibility_date?: string;
+  /**
+   * A list of flags that enable features from upcoming features of the Workers runtime, usually used together with compatibility_date.
+   *
+   * More details at https://developers.cloudflare.com/workers/configuration/compatibility-flags/
+   */
   compatibility_flags?: string[];
-  d1_databases?: WranglerD1Database[];
-  r2_buckets?: WranglerR2Bucket[];
-  kv_namespaces?: WranglerKVNamespace[];
-  vars?: Record<string, string>;
-  env?: Record<string, RawEnvironment>;
-  routes?: Array<{
-    pattern: string;
-    zone_name?: string;
-    custom_domain?: boolean;
-  }>;
-  route?: string;
+  /**
+   * The entrypoint/path to the JavaScript file that will be executed.
+   */
+  main?: string;
+  /**
+   * If true then Wrangler will traverse the file tree below `base_dir`; Any files that match `rules` will be included in the deployed Worker. Defaults to true if `no_bundle` is true, otherwise false.
+   */
+  find_additional_modules?: boolean;
+  /**
+   * Determines whether Wrangler will preserve bundled file names. Defaults to false. If left unset, files will be named using the pattern ${fileHash}-${basename}, for example, `34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico`.
+   */
+  preserve_file_names?: boolean;
+  /**
+   * The directory in which module rules should be evaluated when including additional files into a Worker deployment. This defaults to the directory containing the `main` entry point of the Worker if not specified.
+   */
+  base_dir?: string;
+  /**
+   * Whether we use <name>.<subdomain>.workers.dev to test and deploy your Worker.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workersdev
+   */
+  workers_dev?: boolean;
+  /**
+   * Whether we use <version>-<name>.<subdomain>.workers.dev to serve Preview URLs for your Worker.
+   */
+  preview_urls?: boolean;
+  /**
+   * A list of routes that your Worker should be published to. Only one of `routes` or `route` is required.
+   *
+   * Only required when workers_dev is false, and there's no scheduled Worker (see `triggers`)
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#types-of-routes
+   */
+  routes?: Route[];
+  /**
+   * A route that your Worker should be published to. Literally the same as routes, but only one. Only one of `routes` or `route` is required.
+   *
+   * Only required when workers_dev is false, and there's no scheduled Worker
+   */
+  route?: string | ZoneIdRoute | ZoneNameRoute | CustomDomainRoute;
+  /**
+   * Path to a custom tsconfig
+   */
+  tsconfig?: string;
+  /**
+   * The function to use to replace jsx syntax.
+   */
+  jsx_factory?: string;
+  /**
+   * The function to use to replace jsx fragment syntax.
+   */
+  jsx_fragment?: string;
+  /**
+   * A list of migrations that should be uploaded with your Worker.
+   *
+   * These define changes in your Durable Object declarations.
+   *
+   * More details at https://developers.cloudflare.com/workers/learning/using-durable-objects#configuring-durable-object-classes-with-migrations
+   */
+  migrations?: DurableObjectMigration[];
+  /**
+   * "Cron" definitions to trigger a Worker's "scheduled" function.
+   *
+   * Lets you call Workers periodically, much like a cron job.
+   *
+   * More details here https://developers.cloudflare.com/workers/platform/cron-triggers
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#triggers
+   */
+  triggers?: {
+    crons?: string[];
+  };
+  /**
+   * Specify limits for runtime behavior. Only supported for the "standard" Usage Model
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#limits
+   */
+  limits?: {
+    /**
+     * Maximum allowed CPU time for a Worker's invocation in milliseconds
+     */
+    cpu_ms?: number;
+    /**
+     * Maximum allowed number of fetch requests that a Worker's invocation can execute
+     */
+    subrequests?: number;
+  };
+  /**
+   * An ordered list of rules that define which modules to import, and what type to import them as. You will need to specify rules to use Text, Data, and CompiledWasm modules, or when you wish to have a .js file be treated as an ESModule instead of CommonJS.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#bundling
+   */
+  rules?: Rule[];
+  /**
+   * Configures a custom build step to be run by Wrangler when building your Worker.
+   *
+   * Refer to the [custom builds documentation](https://developers.cloudflare.com/workers/cli-wrangler/configuration#build) for more details.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#custom-builds
+   */
+  build?: {
+    /**
+     * The command used to build your Worker. On Linux and macOS, the command is executed in the `sh` shell and the `cmd` shell for Windows. The `&&` and `||` shell operators may be used.
+     */
+    command?: string;
+    /**
+     * The directory in which the command is executed.
+     */
+    cwd?: string;
+    /**
+     * The directory to watch for changes while using wrangler dev, defaults to the current working directory
+     */
+    watch_dir?: string | string[];
+  };
+  /**
+   * Skip internal build steps and directly deploy script
+   */
+  no_bundle?: boolean;
+  /**
+   * Minify the script before uploading.
+   */
+  minify?: boolean;
+  /**
+   * Set the `name` property to the original name for functions and classes renamed during minification.
+   *
+   * See https://esbuild.github.io/api/#keep-names
+   */
+  keep_names?: boolean;
+  /**
+   * Designates this Worker as an internal-only "first-party" Worker.
+   */
+  first_party_worker?: boolean;
+  /**
+   * List of bindings that you will send to logfwdr
+   */
+  logfwdr?: {
+    bindings: {
+      /**
+       * The binding name used to refer to logfwdr
+       */
+      name: string;
+      /**
+       * The destination for this logged message
+       */
+      destination: string;
+    }[];
+  };
+  /**
+   * Send Trace Events from this Worker to Workers Logpush.
+   *
+   * This will not configure a corresponding Logpush job automatically.
+   *
+   * For more information about Workers Logpush, see: https://blog.cloudflare.com/logpush-for-workers/
+   */
+  logpush?: boolean;
+  /**
+   * Include source maps when uploading this worker.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#source-maps
+   */
+  upload_source_maps?: boolean;
+  /**
+   * Specify how the Worker should be located to minimize round-trip time.
+   *
+   * More details: https://developers.cloudflare.com/workers/platform/smart-placement/
+   */
+  placement?: {
+    mode: "off" | "smart";
+    hint?: string;
+  } | {
+    mode?: "targeted";
+    region: string;
+  } | {
+    mode?: "targeted";
+    host: string;
+  } | {
+    mode?: "targeted";
+    hostname: string;
+  };
+  /**
+   * Specify the directory of static assets to deploy/serve
+   *
+   * More details at https://developers.cloudflare.com/workers/frameworks/
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#assets
+   */
   assets?: {
+    /**
+     * Absolute path to assets directory
+     */
+    directory?: string;
+    /**
+     * Name of `env` binding property in the User Worker.
+     */
     binding?: string;
-    directory: string;
+    /**
+     * How to handle HTML requests.
+     */
+    html_handling?: "auto-trailing-slash" | "force-trailing-slash" | "drop-trailing-slash" | "none";
+    /**
+     * How to handle requests that do not match an asset.
+     */
+    not_found_handling?: "single-page-application" | "404-page" | "none";
+    /**
+     * Matches will be routed to the User Worker, and matches to negative rules will go to the Asset Worker.
+     *
+     * Can also be `true`, indicating that every request should be routed to the User Worker.
+     */
+    run_worker_first?: string[] | boolean;
+  };
+  /**
+   * Specify the observability behavior of the Worker.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#observability
+   */
+  observability?: {
+    /**
+     * If observability is enabled for this Worker
+     */
+    enabled?: boolean;
+    /**
+     * The sampling rate
+     */
+    head_sampling_rate?: number;
+    logs?: {
+      enabled?: boolean;
+      /**
+       * The sampling rate
+       */
+      head_sampling_rate?: number;
+      /**
+       * Set to false to disable invocation logs
+       */
+      invocation_logs?: boolean;
+      /**
+       * If logs should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
+       */
+      persist?: boolean;
+      /**
+       * What destinations logs emitted from the Worker should be sent to.
+       */
+      destinations?: string[];
+    };
+    traces?: {
+      enabled?: boolean;
+      /**
+       * The sampling rate
+       */
+      head_sampling_rate?: number;
+      /**
+       * If traces should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
+       */
+      persist?: boolean;
+      /**
+       * What destinations traces emitted from the Worker should be sent to.
+       */
+      destinations?: string[];
+    };
+  };
+  /**
+   * Specify the compliance region mode of the Worker.
+   *
+   * Although if the user does not specify a compliance region, the default is `public`, it can be set to `undefined` in configuration to delegate to the CLOUDFLARE_COMPLIANCE_REGION environment variable.
+   */
+  compliance_region?: "public" | "fedramp_high";
+  /**
+   * Configuration for Python modules.
+   */
+  python_modules?: {
+    /**
+     * A list of glob patterns to exclude files from the python_modules directory when bundling.
+     *
+     * Patterns are relative to the python_modules directory and use glob syntax.
+     */
+    exclude: string[];
+  };
+  /**
+   * A map of values to substitute when deploying your Worker.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  define?: {
+    [k: string]: string;
+  };
+  /**
+   * A map of environment variables to set when deploying your Worker.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
+   */
+  vars?: {
+    [k: string]: string | Json;
+  };
+  /**
+   * Secrets configuration (experimental).
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  secrets?: {
+    /**
+     * List of secret names that are required by your Worker. When defined, this property:
+     * - Replaces .dev.vars/.env/process.env inference for type generation
+     * - Enables local dev validation with warnings for missing secrets
+     */
+    required?: string[];
+  };
+  /**
+   * A list of durable objects that your Worker should be bound to.
+   *
+   * For more information about Durable Objects, see the documentation at https://developers.cloudflare.com/workers/learning/using-durable-objects
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#durable-objects
+   */
+  durable_objects?: {
+    bindings: DurableObjectBindings;
+  };
+  /**
+   * A list of workflows that your Worker should be bound to.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  workflows?: WorkflowBinding[];
+  /**
+   * Cloudchamber configuration
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  cloudchamber?: {
+    image?: string;
+    location?: string;
+    instance_type?: "dev" | "basic" | "standard" | "lite" | "standard-1" | "standard-2" | "standard-3" | "standard-4";
+    vcpu?: number;
+    memory?: string;
+    ipv4?: boolean;
+  };
+  /**
+   * Container related configuration
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  containers?: ContainerApp[];
+  /**
+   * These specify any Workers KV Namespaces you want to access from inside your Worker.
+   *
+   * To learn more about KV Namespaces, see the documentation at https://developers.cloudflare.com/workers/learning/how-kv-works
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#kv-namespaces
+   */
+  kv_namespaces?: {
+    /**
+     * The binding name used to refer to the KV Namespace
+     */
+    binding: string;
+    /**
+     * The ID of the KV namespace
+     */
+    id?: string;
+    /**
+     * The ID of the KV namespace used during `wrangler dev`
+     */
+    preview_id?: string;
+    /**
+     * Whether the KV namespace should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * These specify bindings to send email from inside your Worker.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#email-bindings
+   */
+  send_email?: {
+    /**
+     * The binding name used to refer to the this binding
+     */
+    name: string;
+    /**
+     * If this binding should be restricted to a specific verified address
+     */
+    destination_address?: string;
+    /**
+     * If this binding should be restricted to a set of verified addresses
+     */
+    allowed_destination_addresses?: string[];
+    /**
+     * If this binding should be restricted to a set of sender addresses
+     */
+    allowed_sender_addresses?: string[];
+    /**
+     * Whether the binding should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies Queues that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#queues
+   */
+  queues?: {
+    /**
+     * Producer bindings
+     */
+    producers?: {
+      /**
+       * The binding name used to refer to the Queue in the Worker.
+       */
+      binding: string;
+      /**
+       * The name of this Queue.
+       */
+      queue: string;
+      /**
+       * The number of seconds to wait before delivering a message
+       */
+      delivery_delay?: number;
+      /**
+       * Whether the Queue producer should be remote or not in local development
+       */
+      remote?: boolean;
+    }[];
+    /**
+     * Consumer configuration
+     */
+    consumers?: {
+      /**
+       * The name of the queue from which this consumer should consume.
+       */
+      queue: string;
+      /**
+       * The consumer type, e.g., worker, http-pull, r2-bucket, etc. Default is worker.
+       */
+      type?: string;
+      /**
+       * The maximum number of messages per batch
+       */
+      max_batch_size?: number;
+      /**
+       * The maximum number of seconds to wait to fill a batch with messages.
+       */
+      max_batch_timeout?: number;
+      /**
+       * The maximum number of retries for each message.
+       */
+      max_retries?: number;
+      /**
+       * The queue to send messages that failed to be consumed.
+       */
+      dead_letter_queue?: string;
+      /**
+       * The maximum number of concurrent consumer Worker invocations. Leaving this unset will allow your consumer to scale to the maximum concurrency needed to keep up with the message backlog.
+       */
+      max_concurrency?: number | null;
+      /**
+       * The number of milliseconds to wait for pulled messages to become visible again
+       */
+      visibility_timeout_ms?: number;
+      /**
+       * The number of seconds to wait before retrying a message
+       */
+      retry_delay?: number;
+    }[];
   };
-  [key: string]: unknown;
+  /**
+   * Specifies R2 buckets that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#r2-buckets
+   */
+  r2_buckets?: {
+    /**
+     * The binding name used to refer to the R2 bucket in the Worker.
+     */
+    binding: string;
+    /**
+     * The name of this R2 bucket at the edge.
+     */
+    bucket_name?: string;
+    /**
+     * The preview name of this R2 bucket at the edge.
+     */
+    preview_bucket_name?: string;
+    /**
+     * The jurisdiction that the bucket exists in. Default if not present.
+     */
+    jurisdiction?: string;
+    /**
+     * Whether the R2 bucket should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies D1 databases that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#d1-databases
+   */
+  d1_databases?: {
+    /**
+     * The binding name used to refer to the D1 database in the Worker.
+     */
+    binding: string;
+    /**
+     * The name of this D1 database.
+     */
+    database_name?: string;
+    /**
+     * The UUID of this D1 database (not required).
+     */
+    database_id?: string;
+    /**
+     * The UUID of this D1 database for Wrangler Dev (if specified).
+     */
+    preview_database_id?: string;
+    /**
+     * The name of the migrations table for this D1 database (defaults to 'd1_migrations').
+     */
+    migrations_table?: string;
+    /**
+     * The path to the directory of migrations for this D1 database (defaults to './migrations').
+     */
+    migrations_dir?: string;
+    /**
+     * Internal use only.
+     */
+    database_internal_env?: string;
+    /**
+     * Whether the D1 database should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies Vectorize indexes that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#vectorize-indexes
+   */
+  vectorize?: {
+    /**
+     * The binding name used to refer to the Vectorize index in the Worker.
+     */
+    binding: string;
+    /**
+     * The name of the index.
+     */
+    index_name: string;
+    /**
+     * Whether the Vectorize index should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies Hyperdrive configs that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#hyperdrive
+   */
+  hyperdrive?: {
+    /**
+     * The binding name used to refer to the project in the Worker.
+     */
+    binding: string;
+    /**
+     * The id of the database.
+     */
+    id: string;
+    /**
+     * The local database connection string for `wrangler dev`
+     */
+    localConnectionString?: string;
+  }[];
+  /**
+   * Specifies service bindings (Worker-to-Worker) that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#service-bindings
+   */
+  services?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * The name of the service. To bind to a worker in a specific environment, you should use the format `<worker_name>-<environment_name>`.
+     */
+    service: string;
+    /**
+     * Optionally, the entrypoint (named export) of the service to bind to.
+     */
+    entrypoint?: string;
+    /**
+     * Optional properties that will be made available to the service via ctx.props.
+     */
+    props?: {
+      [k: string]: unknown;
+    };
+    /**
+     * Whether the service binding should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies analytics engine datasets that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#analytics-engine-datasets
+   */
+  analytics_engine_datasets?: {
+    /**
+     * The binding name used to refer to the dataset in the Worker.
+     */
+    binding: string;
+    /**
+     * The name of this dataset to write to.
+     */
+    dataset?: string;
+  }[];
+  /**
+   * A browser that will be usable from the Worker.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#browser-rendering
+   */
+  browser?: {
+    binding: string;
+    /**
+     * Whether the Browser binding should be remote or not in local development
+     */
+    remote?: boolean;
+  };
+  /**
+   * Binding to the AI project.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workers-ai
+   */
+  ai?: {
+    binding: string;
+    staging?: boolean;
+    /**
+     * Whether the AI binding should be remote or not in local development
+     */
+    remote?: boolean;
+  };
+  /**
+   * Binding to Cloudflare Images
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#images
+   */
+  images?: {
+    binding: string;
+    /**
+     * Whether the Images binding should be remote or not in local development
+     */
+    remote?: boolean;
+  };
+  /**
+   * Binding to Cloudflare Media Transformations
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  media?: {
+    binding: string;
+    /**
+     * Whether the Media binding should be remote or not
+     */
+    remote?: boolean;
+  };
+  /**
+   * Binding to the Worker Version's metadata
+   */
+  version_metadata?: {
+    binding: string;
+  };
+  /**
+   * "Unsafe" tables for features that aren't directly supported by wrangler.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  unsafe?: {
+    /**
+     * A set of bindings that should be put into a Worker's upload metadata without changes. These can be used to implement bindings for features that haven't released and aren't supported directly by wrangler or miniflare.
+     */
+    bindings?: {
+      /**
+       * The name of the binding provided to the Worker
+       */
+      name: string;
+      /**
+       * The 'type' of the unsafe binding.
+       */
+      type: string;
+      dev?: {
+        plugin: {
+          /**
+           * Package is the bare specifier of the package that exposes plugins to integrate into Miniflare via a named `plugins` export.
+           */
+          package: string;
+          /**
+           * Plugin is the name of the plugin exposed by the package.
+           */
+          name: string;
+        };
+        /**
+         * Optional mapping of unsafe bindings names to options provided for the plugin.
+         */
+        options?: {
+          [k: string]: unknown;
+        };
+      };
+      [k: string]: unknown;
+    }[];
+    /**
+     * Arbitrary key/value pairs that will be included in the uploaded metadata.  Values specified here will always be applied to metadata last, so can add new or override existing fields.
+     */
+    metadata?: {
+      [k: string]: unknown;
+    };
+    /**
+     * Used for internal capnp uploads for the Workers runtime
+     */
+    capnp?: {
+      base_path: string;
+      source_schemas: string[];
+    } | {
+      compiled_schema: string;
+    };
+  };
+  /**
+   * Specifies a list of mTLS certificates that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#mtls-certificates
+   */
+  mtls_certificates?: {
+    /**
+     * The binding name used to refer to the certificate in the Worker
+     */
+    binding: string;
+    /**
+     * The uuid of the uploaded mTLS certificate
+     */
+    certificate_id: string;
+    /**
+     * Whether the mtls fetcher should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies a list of Tail Workers that are bound to this Worker environment
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  tail_consumers?: TailConsumer[];
+  /**
+   * Specifies a list of Streaming Tail Workers that are bound to this Worker environment
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  streaming_tail_consumers?: StreamingTailConsumer[];
+  /**
+   * Specifies namespace bindings that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#dispatch-namespace-bindings-workers-for-platforms
+   */
+  dispatch_namespaces?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * The namespace to bind to.
+     */
+    namespace: string;
+    /**
+     * Details about the outbound Worker which will handle outbound requests from your namespace
+     */
+    outbound?: {
+      /**
+       * Name of the service handling the outbound requests
+       */
+      service: string;
+      /**
+       * (Optional) Name of the environment handling the outbound requests.
+       */
+      environment?: string;
+      /**
+       * (Optional) List of parameter names, for sending context from your dispatch Worker to the outbound handler
+       */
+      parameters?: string[];
+    };
+    /**
+     * Whether the Dispatch Namespace should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies list of Pipelines bound to this Worker environment
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  pipelines?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * Name of the Pipeline to bind
+     */
+    pipeline: string;
+    /**
+     * Whether the pipeline should be remote or not in local development
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * Specifies Secret Store bindings that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  secrets_store_secrets?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * Id of the secret store
+     */
+    store_id: string;
+    /**
+     * Name of the secret
+     */
+    secret_name: string;
+  }[];
+  /**
+   * **DO NOT USE**. Hello World Binding Config to serve as an explanatory example.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  unsafe_hello_world?: {
+    /**
+     * The binding name used to refer to the bound service.
+     */
+    binding: string;
+    /**
+     * Whether the timer is enabled
+     */
+    enable_timer?: boolean;
+  }[];
+  /**
+   * Specifies rate limit bindings that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  ratelimits?: {
+    /**
+     * The binding name used to refer to the rate limiter in the Worker.
+     */
+    name: string;
+    /**
+     * The namespace ID for this rate limiter.
+     */
+    namespace_id: string;
+    /**
+     * Simple rate limiting configuration.
+     */
+    simple: {
+      /**
+       * The maximum number of requests allowed in the time period.
+       */
+      limit: number;
+      /**
+       * The time period in seconds (10 for ten seconds, 60 for one minute).
+       */
+      period: 10 | 60;
+    };
+  }[];
+  /**
+   * Specifies Worker Loader bindings that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  worker_loaders?: {
+    /**
+     * The binding name used to refer to the Worker Loader in the Worker.
+     */
+    binding: string;
+  }[];
+  /**
+   * Specifies VPC services that are bound to this Worker environment.
+   *
+   * NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
+   */
+  vpc_services?: {
+    /**
+     * The binding name used to refer to the VPC service in the Worker.
+     */
+    binding: string;
+    /**
+     * The service ID of the VPC connectivity service.
+     */
+    service_id: string;
+    /**
+     * Whether the VPC service is remote or not
+     */
+    remote?: boolean;
+  }[];
+  /**
+   * The directory of static assets to serve.
+   *
+   * The presence of this field in a Wrangler configuration file indicates a Pages project, and will prompt the handling of the configuration file according to the Pages-specific validation rules.
+   */
+  pages_build_output_dir?: string;
+  /**
+   * A boolean to enable "legacy" style wrangler environments (from Wrangler v1). These have been superseded by Services, but there may be projects that won't (or can't) use them. If you're using a legacy environment, you can set this to `true` to enable it.
+   */
+  legacy_env?: boolean;
+  /**
+   * Whether Wrangler should send usage metrics to Cloudflare for this project.
+   *
+   * When defined this will override any user settings. Otherwise, Wrangler will use the user's preference.
+   */
+  send_metrics?: boolean;
+  /**
+   * Options to configure the development server that your worker will use.
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#local-development-settings
+   */
+  dev?: {
+    /**
+     * IP address for the local dev server to listen on,
+     */
+    ip?: string;
+    /**
+     * Port for the local dev server to listen on
+     */
+    port?: number;
+    /**
+     * Port for the local dev server's inspector to listen on
+     */
+    inspector_port?: number;
+    /**
+     * IP address for the local dev server's inspector to listen on
+     */
+    inspector_ip?: string;
+    /**
+     * Protocol that local wrangler dev server listens to requests on.
+     */
+    local_protocol?: "http" | "https";
+    /**
+     * Protocol that wrangler dev forwards requests on
+     *
+     * Setting this to `http` is not currently implemented for remote mode. See https://github.com/cloudflare/workers-sdk/issues/583
+     */
+    upstream_protocol?: "https" | "http";
+    /**
+     * Host to forward requests to, defaults to the host of the first route of project
+     */
+    host?: string;
+    /**
+     * When developing, whether to build and connect to containers. This requires a Docker daemon to be running. Defaults to `true`.
+     */
+    enable_containers?: boolean;
+    /**
+     * Either the Docker unix socket i.e. `unix:///var/run/docker.sock` or a full configuration. Note that windows is only supported via WSL at the moment
+     */
+    container_engine?: {
+      localDocker: DockerConfiguration;
+    } | string;
+    /**
+     * Re-generate your worker types when your Wrangler configuration file changes.
+     */
+    generate_types?: boolean;
+  };
+  /**
+   * The definition of a Worker Site, a feature that lets you upload static assets with your Worker.
+   *
+   * More details at https://developers.cloudflare.com/workers/platform/sites
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workers-sites
+   */
+  site?: {
+    /**
+     * The directory containing your static assets.
+     *
+     * It must be a path relative to your Wrangler configuration file. Example: bucket = "./public"
+     *
+     * If there is a `site` field then it must contain this `bucket` field.
+     */
+    bucket: string;
+    /**
+     * @deprecated
+     * The location of your Worker script.
+     */
+    "entry-point"?: string;
+    /**
+     * An exclusive list of .gitignore-style patterns that match file or directory names from your bucket location. Only matched items will be uploaded. Example: include = ["upload_dir"]
+     */
+    include?: string[];
+    /**
+     * A list of .gitignore-style patterns that match files or directories in your bucket that should be excluded from uploads. Example: exclude = ["ignore_dir"]
+     */
+    exclude?: string[];
+  };
+  /**
+   * A list of wasm modules that your worker should be bound to. This is the "legacy" way of binding to a wasm module. ES module workers should do proper module imports.
+   */
+  wasm_modules?: {
+    [k: string]: string;
+  };
+  /**
+   * A list of text files that your worker should be bound to. This is the "legacy" way of binding to a text file. ES module workers should do proper module imports.
+   */
+  text_blobs?: {
+    [k: string]: string;
+  };
+  /**
+   * A list of data files that your worker should be bound to. This is the "legacy" way of binding to a data file. ES module workers should do proper module imports.
+   */
+  data_blobs?: {
+    [k: string]: string;
+  };
+  /**
+   * A map of module aliases. Lets you swap out a module for any others. Corresponds with esbuild's `alias` config
+   *
+   * For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#module-aliasing
+   */
+  alias?: {
+    [k: string]: string;
+  };
+  /**
+   * By default, the Wrangler configuration file is the source of truth for your environment configuration, like a terraform file.
+   *
+   * If you change your vars in the dashboard, wrangler *will* override/delete them on its next deploy.
+   *
+   * If you want to keep your dashboard vars when wrangler deploys, set this field to true.
+   */
+  keep_vars?: boolean;
 }
-/** Alias for RawConfig (user-friendly name) */
+//#endregion
+//#region src/generated/wrangler-types.d.ts
+/** Alias for RawConfig */
 type WranglerConfig = RawConfig;
 /** Alias for RawEnvironment */
 type WranglerEnvironment = RawEnvironment;
+/** D1 database binding — extracted from RawConfig */
+type WranglerD1Database = NonNullable<RawConfig["d1_databases"]>[number];
+/** R2 bucket binding — extracted from RawConfig */
+type WranglerR2Bucket = NonNullable<RawConfig["r2_buckets"]>[number];
+/** KV namespace binding — extracted from RawConfig */
+type WranglerKVNamespace = NonNullable<RawConfig["kv_namespaces"]>[number];
 //#endregion
 export { type RawConfig, type RawEnvironment, type WranglerConfig, type WranglerD1Database, type WranglerEnvironment, type WranglerKVNamespace, type WranglerR2Bucket };
 //# sourceMappingURL=index.d.mts.map