Wrangler Automatic resource provisioning not working with vite

[twilit crest]

I see the news that wrangler now can auto provision resources without specifying resource id in the config file, so I updated wrangler to 4.45.0, and put D1 binding in my wrangler.jsonc

"d1_databases": [
        {
            "binding": "DB",
            "migrations_dir": "drizzle",
            "remote": true
        }
    ]

but when I try to run dev server or to deploy I got this error

✗ pn dev       

> .@ dev /home/kuang/projects/blog
> vite dev --port 3000

error when starting dev server:
Error: Processing wrangler.jsonc configuration:
  - "d1_databases[0]" bindings must have a "database_id" field but got {"binding":"DB","migrations_dir":"drizzle","remote":true}.
    at readConfig (/home/kuang/projects/blog/node_modules/.pnpm/[email protected]/node_modules/wrangler/wrangler-dist/cli.js:121404:11)
    at readWorkerConfig (file:///home/kuang/projects/blog/node_modules/.pnpm/@[email protected][email protected]_@[email protected][email protected]_lightningcs_5f4b83851e586ed5c812c54731415fe4/node_modules/@cloudflare/vite-plugin/dist/index.js:15350:17)

[solemn vector]

Thanks for reporting this! I've just reproduced it with a standard react + vite plugin create cloudflare app with some bindings without resources and I get the same thing as you. I'll bring it up with the team next week 👍

[solemn vector]

Hey @twilit crest - we're aware we have a bug in this where sometimes the flag for the auto provision is not being passed, we're going to try and get that in this week, I'll let you know when that rolls around.

Another note on this is that we've decided intentionally to not support 'remote' flagged bindings being created automatically, as our thinking is that you would only use 'remote' if you cared about the data, and wanted to share it, and by its nature not having an ID conflicts with that. However, we are open to discussion on this, so if you have an interesting use case we would love to hear it!