Cloudflare

It might work with just the `export class MyDOClass`, but if it doesn't just add the `export default {}`.

do you have any suggestions for dev mode? should I be mocking out the worker interface? my code will be going through `env.BINDING.etc`

because I'd be using pages, I can't just use `wrangler pages dev` afaik

I could theoretically hit a different environment dev DO, but that seems wasteful on $ and requires connectivity while dev'ing

`wrangler` should be able to connect to a DO automatically. If you run `wrangler dev` in your Worker, and then `wrangler pages dev dist --do BINDING=MyDOClass`, they should be able to link together...

Yeah, afaik you should `export class` and `export default`

Though this will probably need to be `--do BINDING=MyWorkerName@MyDoClass`

next I'm wondering if I should manage all DOs as 1 wrangler package, or make each with their own wrangler.toml

dont think it matters that much but do note that when you deploy a worker all DOs will reset all active connections to do a code update and might throw some errors for a second or so

`--do COUNTER=my_worker_name@Counter` does not seem to be working unfortunately

I verified in cloudflare dash that it was published with `my_worker_name`

made the bindings in the pages project via dash

bound it as `COUNTER` and it has Durable object namespace of `my_worker_name_Counter`

`[pages:err] DurableObjectError [ERR_CLASS_NOT_FOUND]: Class "Counter" for Durable Object "COUNTER" not found`

Are you also running `wrangler dev --local` for your other worker name?

`yarn wrangler pages dev ./dist --compatibility-date=2023-03-04 --do COUNTER=my_worker_name@Counter --local`

my DO's toml if that matters
```
name = "my_worker_name"
main = "./dist/index.mjs"
compatibility_date = "2023-03-06"

[build]
command = "yarn install && yarn build"

[durable_objects]
bindings = [{name = "COUNTER", class_name = "Counter"}]

[[migrations]]
tag = "v1" # Should be unique for each entry
new_classes = ["Counter"]
```

surely I don't need to redeploy the pages project @ CF right? since this is local

https://developers.cloudflare.com/pages/platform/functions/bindings/#durable-object-namespaces

For local dev, nothing matters about what's on production

Can you also share the command you're running the DO worker from?

```
class Counter {
    state;
    value;
    constructor(state) {
        this.state = state;
        // `blockConcurrencyWhile()` ensures no requests are delivered until initialization completes.
        this.state.blockConcurrencyWhile(async () => {
            const stored = (await this.state.storage.get("value"));
            this.value = stored || 0;
        });
    }
    async fetch(request) {
        const url = new URL(request.url);
        let currentValue = this.value;
        if (url.pathname === "/increment") {
            currentValue = ++this.value;
            await this.state.storage.put("value", currentValue);
        }
        return new Response(JSON.stringify(this.value), {
            headers: { "Content-Type": "application/json" },
        });
    }
}

var index = {};
console.log("wtf mate");

export { Counter, index as default };
``` 
this dist/index.mjs <@312617227490951168>

which looks correct to me afaict & does console.log

```
yarn wrangler dev --local
yarn run v1.22.19
$ /home/redacted/projects/redacted/durable_objects/node_modules/.bin/wrangler dev --local
 ⛅️ wrangler 2.12.0 
--------------------
Want to try out the next version of local mode using the open-source Workers runtime?
Switch out --local for --experimental-local and let us know what you think at https://discord.gg/cloudflaredev !
Running custom build: yarn install && yarn build
[1/4] Resolving packages...
success Already up-to-date.
$ rollup -c

src/index.ts → dist/index.mjs...
created dist/index.mjs in 595ms
Your worker has access to the following bindings:
- Durable Objects:
  - COUNTER: Counter
⎔ Starting a local server...
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit           │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Debugger listening on ws://127.0.0.1:36049/9bcc17cf-b793-48a4-8a64-47051ea02018
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
wtf mate
[mf:inf] Worker reloaded! (0.72KiB)
[mf:inf] Listening on 0.0.0.0:8787
[mf:inf] - http://127.0.0.1:8787
[mf:inf] - http://172.17.94.145:8787
[mf:inf] Updated `Request.cf` object cache!
```

This shouldn't make a difference, but which order are you running them in?

Can you make a minimal reproducible repo that I can try?

let me try to see if some aspect of my Pages build hasn't messed with it, I was trying to use DO's within Pages before, so I have some exports of similar named objects

I had this in there:
```
[durable_objects]
bindings = [
  { name = 'COUNTER', class_name = 'Counter' }
]

[[migrations]]
tag = "v1" # Should be unique for each entry
new_classes = ["Counter"]
```

so it was erroring about the wrangler.toml

--do BINDING=workername@ClassName seems to be the syntax

I wouldn't have ever thought of that causing it

tyvm for your help, hopefully it's now connected, I'll try getting data out of it now

Thank y'all for documenting this discussion / would have never got there on my own today

Are DO auto-migrations (moving the data and DO closer to where it is being consistently accessed) still something Cloudflare is considering for the future? Is it still a ways out, or is it going to be worked on "soon"?

not actively being worked on but in planning, if you have feedback on your use case / what you're expecting to gain / what you want to avoid I'd be curious to hear