https://discord.cloudflare.com logo
Join Discord
Powered by
# durable-objects
  • a
    or even just browse what exists?
  • w
    Are durable object automatic retries for alerts billed as additional request?
  • a
    mind re-uploading this? would love to see how you managed to figure this out. i'm struggling to create what should be an incredibly simple proof of concept: Pages + a single durable object.
  • a
    this is my dev command: 
    wrangler pages dev --local --do=COUNTER=Counter -- vite dev
  • h
    You need a second Worker, also running dev
    a
    f
    z
    • 4
    • 23
  • c
  • a
    thanks - this tells me which DOs have data attached, but I want to actually download/export that data. any way to do that?
  • c
    for each of those DOs, request the data that you want
  • c
    there's no built in bulk export
  • f
    is it possible to add a service binding for a durable object without writing a toml file? I'm adding 
    --do THING=Thing
    to 
    wrangler pages dev
    but all I get is a 
    DurableObjectError [ERR_CLASS_NOT_FOUND]
    . I'm basically trying to add a binding for durable objects to a Pages/Functions project
  • f
    From `wrangler pages dev --help`: 
    --do Durable Object to bind (--do NAME=CLASS) [array]
    Where does this class export live? I've tried putting it in the pages function, in the functions directory, in the src/ directory and at the root
  • m
    Attempting to add DO bindings and not seeing the option on our account (paid tier) -- are the instructions wrong or something off with our accounts? This is for Pages, at the moment.
  • w
    It looks like you have no published DOs
  • w
    Have you created any?
  • m
    Definitely not, that wasn't clear from the Pages docs -- thanks for the heads up, I'll dig into the Workers docs.
  • u
    The message on the dashboard says you have no durable objects created not really sure how they could make that more clear but I'm sure suggestions could be helpful
  • h
    You have to run a separate 
    wrangler dev
    session which declares the DO
  • j
    I'm also trying to achieve the same as four33. I have two repos: a pages project, and a worker that exports a 
    Player
    DO class. I'm running 
    wrangler dev
    inside the worker repo, but running 
    wrangler pages dev --do players=Player
    in my pages project yields 
    DurableObjectError [ERR_CLASS_NOT_FOUND]: Class "Player" for Durable Object "player" not found
    . I'm assuming I'm either doing something wrong when running the pages command, or maybe the worker's 
    wrangler.toml
    is missing something? The worker itself works fine when I publish it, and the DO appears as possible bindings in the pages dashboard. Is there anything else I should do to "declare the DO" locally? Appreciate any pointers you might have 😊
  • h
    I believe the command for Pages would be
    Copy code
    sh
wrangler pages dev --do players=Player@WorkerScriptName
    , and replace 
    WorkerScriptName
    with the name of the script that exposes your 
    Player
    DO class.
  • j
    Wow, that did the trick! Thanks a bunch!
  • f
    Thanks for the help!
  • f
    @Unsmart | Tech debt I think the dashboard is clear, but I think there's obviously a bit of confusion about using durable objects with Pages. It's not immediately apparent that you have to create a separate wrangler config/run another wrangler session to populate the DO. I guess I would have expected a class export from a function to get picked up by 
    wrangler pages dev
    with the 
    --do
    flag.
  • f
    What's the trick to getting these bindings working locally with pages dev? I have a durable object + a worker published, I'm pointing to it with the 
    --do
    flag, but my 
    context.env
    doesn't contain that Durable Object namespace
  • f
    wrangler dev --local
  • h
    How are you testing whether it exists?
  • f
    I was just logging context.env
  • f
    but resolved now, running 
    wrangler dev --local
    from my worker
  • h
    It shouldn’t resolve. IIIRC, the env object isn’t serializable, so it should just log as 
    {}
  • f
    nah it does
  • f
    Copy code
    console.log(context.env)

{
  KV_NAMESPACE: KVNamespace,
  SOME_ENV_VAR: 'abc123',
  DO_NAMESPACE: DurableObjectNamespace
}
    etc
1...525526527...567Latest