Proposal: Support for wrangler.config.[tj]s formats for Wrangler Configuration, For more flexible configuration.

[sonofmagic]

Currently, the configuration methods using wrangler.jsonc and wrangler.toml are not flexible enough.

In many cases, we want to dynamically fetch data from local or remote sources and apply it to our deployment configuration, but this is not possible at the moment.

For Example:

{
  // wrangler.jsonc
  "$schema": "./node_modules/wrangler/config-schema.json",
  "name": "monorepo-service",
  "compatibility_date": "2025-09-15",
  "main": "./src/fetch-enrty.ts",
  "assets": {
    "directory": "./dist",
    "binding": "ASSETS",
    "not_found_handling": "single-page-application"
  },
}

// wrangler.config.ts
import { defineConfig } from 'wrangler'
import 'dotenv/config'
import process from 'node:process'
export default defineConfig(async ()=>{
  const remoteConfig =  await fetchConfig()
  return {
    name: process.env.CF_WORKER_NAME,
    compatibility_date:'2025-09-15',
    ...remoteConfig
  }
})

[timkelty]

Even without the need to fetch data, the non-inheritability of bindings means tons of replication when using wrangler environments.
As .js/.ts, you could compose them more reasonably.

[salimauid193-source]