Cloudflare

the API response from wrangler seems to include the handlers

```toml
bindings = [
    { name = "rooms", class_name= "ChatRoom" },
    { name = "limiters", class_name = "RateLimiter" }
]
```

oh well, theres no mention of the term ``rooms`` anywhere in the requests wrangler uses to upload the worker.

```toml
type = 'javascript'
name = "coincrash-dev"
account_id = '009cb107e5dbe5802252ce09d6a0e301'
route = 'dev.coincrash.com/*'
zone_id = 'bb7c0c340ce129139faac2ee87806ce9'

[site]
bucket = "./build"

[env.staging]
name = 'coincrash-staging'
zone_id='bb7c0c340ce129139faac2ee87806ce9'
route = 'staging.coincrash.com/*'

[env.production]
name = 'coincrash'
zone_id='bb7c0c340ce129139faac2ee87806ce9'
route = 'coincrash.com/*'

[env.test]
name='coincrash_test'
zone_id='bb7c0c340ce129139faac2ee87806ce9'
route = 'test.coincrash.com/*'


[build]
command = 'npm install && npm run build'
[build.upload]
format = 'modules'
dir = 'workers-site'
main = './index.mjs'

[durable_objects]
bindings = [
    { name = "rooms", class_name= "ChatRoom" },
    { name = "limiters", class_name = "RateLimiter" }
]
```

im not sure but the bindings dont appear to be working

its supposed to work, usually i use the "env.EXAMPLE_CLASS.idFromName" notation.
One small question, did you pass --new-class ChatRoom --new-class RateLimiter to you publish?

maybe I can look at the wrangler source code

will raise a error if the class already exists

I already got wrangler to work with KV and modular code

so it already can tell if it exists, but doesnt add it. Interesting.

that added ``new_classes`` to the metadata

<@!281963256967331840> what environment are you testing it?

idk where you found that cuz the docs didnt say that as far as I can tell