Your worker names are different for each environment right? If you remove the `environment` and keep

Llambrospetrou Your worker names are different for each environment right? If you remove the `e...

E

Earl•10/14/25, 9:11 AM

Since wrangler automatically suffixes the env name to the worker name it does make sense. What doesn't make sense to me is that the DO binding configuration has an environment property:
https://developers.cloudflare.com/workers/wrangler/configuration/#durable-objects
What does it do?

Cloudflare Docs

Configuration

Use a configuration file to customize the development and deployment setup for your Worker project and other Developer Platform products.

EEarl Since wrangler automatically suffixes the env name to the worker name it does ma...

L

lambrospetrouOP•10/14/25, 9:41 AM

Not sure, but my guess would be it's from the deprecated "service environments" thing that was tried out a few years ago.

BBrayden Durable Objects will have a built in Studio in the dashboard next week if this f...

C

christianklotz•10/14/25, 9:51 AM

Is this GA? My Durable Objects dashboard looks like it still uses the previous design

Llambrospetrou Not sure, but my guess would be it's from the deprecated "service environments" ...

E

Earl•10/14/25, 10:01 AM

Ah alright, thanks!

I

icemelt_melt•10/14/25, 11:14 AM

I want to know will ever Durable Objects or D1 come to Dubai region?

N

Nick•10/14/25, 12:57 PM

Has anyone managed to successfully wrap durable objects classes?

I am looking at how sentry does it:
https://github.com/getsentry/sentry-javascript/blob/develop/packages/cloudflare/src/durableobject.ts
And it's really rather complex!

We want to wrap all the methods on our durable object in an AsyncLocalStorage context but keep getting errors with the wrong

this

this

being bound, or shared IO stuff, or private member access. We tried doing it with a proxy, and then copying the sentry approach. Both got close but had some error conditions like

Cannot perform I/O on behalf of a different Durable Object

Cannot perform I/O on behalf of a different Durable Object

Cannot perform I/O on behalf of a different Durable Object

Cannot perform I/O on behalf of a different Durable Object

or

Cannot read private member #_name from an object whose class did not declare it

Cannot read private member #_name from an object whose class did not declare it

Cannot read private member #_name from an object whose class did not declare it

Cannot read private member #_name from an object whose class did not declare it

.

GitHub

sentry-javascript/packages/cloudflare/src/durableobject.ts at devel...

Official Sentry SDKs for JavaScript. Contribute to getsentry/sentry-javascript development by creating an account on GitHub.

Cchristianklotz Is this GA? My Durable Objects dashboard looks like it still uses the previous d...

B

Brayden•10/14/25, 8:28 PM

....this week

promise!

L

Lulu•10/14/25, 10:23 PM

are there plans to add more jurisdictions for Durable Objects?

E

Earl•10/14/25, 10:40 PM

I have a DO that is defined in worker-a but used in worker-b as well. I generate types for worker-b like this:
wrangler --cwd worker-b types -c wrangler.jsonc -c ../worker-a/wrangler.jsonc

This works and I get the right types when accessing the DO in worker-b.

The problem is that when I run tsc on worker-b I get type errors because the worker-configuration.d.ts imports all of worker-a (and not only the DO class):
interface Env {
do: DurableObjectNamespace<import("../worker-a/src/index").DO>;
}

worker-a uses env variables in code unrelated to the DO that are not available in worker-b which lead to the type error.

What is the recommended architecture for shared DOs? I was thinking of putting them in a separate worker that only holds the DOs and is not actually callable. But I'm not sure if that's how it's meant to be done.

J

JonathanR•10/15/25, 3:54 PM

In the last few weeks we've started to see random

RangeError: Invalid typed array length:

RangeError: Invalid typed array length:

RangeError: Invalid typed array length:

RangeError: Invalid typed array length: in durable objects. The lengths reported are all well within what should be a valid range. It seems like others are having similar issue as well, although those have to do with Prisma, which we are not using.

E

Earl•10/15/25, 9:19 PM

When calling a DO of another worker, will the DO have the env of the calling working or of the worker that hosts the DO?

EEarl When calling a DO of another worker, will the DO have the env of the calling wor...

G

geg•10/15/25, 9:28 PM

host

EEarl I have a DO that is defined in worker-a but used in worker-b as well. I generate...

E

Earl•10/15/25, 10:29 PM

I've opened a bug regarding this (with a reproduction):
https://github.com/cloudflare/workers-sdk/issues/10993

GitHub

Type error using other worker's durable object when workers' Env di...

What versions & operating system are you using? System: OS: Windows 11 10.0.26100 CPU: (12) x64 AMD Ryzen 5 9600X 6-Core Processor Memory: 15.82 GB / 31.11 GB Binaries: Node: 24.7.0 - C:\Users...

S

Silvan•10/16/25, 2:11 PM

the outerbase guys finally cooked

S

Silvan•10/16/25, 2:11 PM

(again)

G

gruntlord6•10/16/25, 2:33 PM

is it showing up yet for anyone? I do not see Data Studio in the dash

L

Larry•10/16/25, 2:43 PM

Huge congrats to Brayden and team on shipping DO Data Studio!

G

gruntlord6•10/16/25, 2:43 PM

I guess maybe it hasn't rolled out to my account yet or something, I'll have to try later. I am hyped to look at it though

Ggruntlord6 I guess maybe it hasn't rolled out to my account yet or something, I'll have to ...

B

boop•10/16/25, 2:44 PM

I refreshed a couple of times and it's now showing up

Bboop I refreshed a couple of times and it's now showing up

G

gruntlord6•10/16/25, 2:44 PM

so did I, but I tried when you said that and it's there now haha

G

gruntlord6•10/16/25, 2:46 PM

This is sick! I was hoping it would list your durable objects but this is 100% an improvement over having to install the outerbase package

G

gruntlord6•10/16/25, 2:47 PM

the bulk dropping of tables would be a nice thing to include though

Ggruntlord6 so did I, but I tried when you said that and it's there now haha

L

lambrospetrouOP•10/16/25, 2:47 PM

It should be open to everyone now, so refresh your dashboards if you don't see it

Llambrospetrou It should be open to everyone now, so refresh your dashboards if you don't see i...

G

gruntlord6•10/16/25, 2:49 PM

any chance you guys are looking at adding the bulk table dropping like the outerbase client had? or at least a way to not have to put in every table name when dropping multiple independently?

B

Brayden•10/16/25, 2:55 PM

told you guys it'd be here "next week"

hope you all enjoy it!!

B

Burrito•10/16/25, 3:07 PM

Is there a way to limit data studio to read only operations?

B

Burrito•10/16/25, 3:22 PM

It would also be nice to have better FTS support, currently they just show as

[object Object]

[object Object]

[object Object]

[object Object].

M

mvgrim•10/16/25, 3:26 PM

Also, seems like the Data Studio doesn't expose KV store data that is backed by the SQLite backend. Would be good to have an ability to query that data. I have some durable objects that use the new SQLite backing, but use the KV store API for its simplicity. I know those drop into a different table/DB in the SQLite store, but it's not exposed in Data Studio.

BBurrito It would also be nice to have better FTS support, currently they just show as `[...

V

Visal .In•10/16/25, 5:22 PM

Will work on it.

VVisal .In Will work on it. 🙂

P

Peps•10/16/25, 9:44 PM

Hey

If you're an Cloudflare employee, any chance you could do the

/cfrole

/cfrole

/cfrole

/cfrole command to get the official employee role? It'll make it more clear you're part of the team

Xxormask I'm sure this is a commonly asked question, but what is my best solution for loc...

L

Larry•10/16/25, 10:27 PM

I just released

@lumenize/testing

@lumenize/testing

@lumenize/testing

@lumenize/testing which builds on

cloudflare:test

cloudflare:test

cloudflare:test

cloudflare:test vitest integration. See: https://lumenize.com/docs/testing/usage#basic-usage. Example:

it('shows basic 5-step test', async () => {
  // 1. Create RPC testing client and Browser instance
  await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
  const browser = new Browser();

  // 2. Pre-populate storage via RPC to call asycn KV API
  await client.ctx.storage.put('count', 10);

  // 3. Make a fetch and RPC call to increment
  const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
  const rpcResult = await client.increment();

  // 4. Confirm that results are as expected
  expect(await resp.text()).toBe('11');
  expect(rpcResult).toBe(12);  // Notice this is a number not a string

  // 5. Verify that storage is correct via RPC
  expect(await client.ctx.storage.kv.get('count')).toBe(12);
});

it('shows basic 5-step test', async () => {
  // 1. Create RPC testing client and Browser instance
  await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
  const browser = new Browser();

  // 2. Pre-populate storage via RPC to call asycn KV API
  await client.ctx.storage.put('count', 10);

  // 3. Make a fetch and RPC call to increment
  const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
  const rpcResult = await client.increment();

  // 4. Confirm that results are as expected
  expect(await resp.text()).toBe('11');
  expect(rpcResult).toBe(12);  // Notice this is a number not a string

  // 5. Verify that storage is correct via RPC
  expect(await client.ctx.storage.kv.get('count')).toBe(12);
});

it('shows basic 5-step test', async () => {
  // 1. Create RPC testing client and Browser instance
  await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
  const browser = new Browser();

  // 2. Pre-populate storage via RPC to call asycn KV API
  await client.ctx.storage.put('count', 10);

  // 3. Make a fetch and RPC call to increment
  const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
  const rpcResult = await client.increment();

  // 4. Confirm that results are as expected
  expect(await resp.text()).toBe('11');
  expect(rpcResult).toBe(12);  // Notice this is a number not a string

  // 5. Verify that storage is correct via RPC
  expect(await client.ctx.storage.kv.get('count')).toBe(12);
});

it('shows basic 5-step test', async () => {
  // 1. Create RPC testing client and Browser instance
  await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
  const browser = new Browser();

  // 2. Pre-populate storage via RPC to call asycn KV API
  await client.ctx.storage.put('count', 10);

  // 3. Make a fetch and RPC call to increment
  const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
  const rpcResult = await client.increment();

  // 4. Confirm that results are as expected
  expect(await resp.text()).toBe('11');
  expect(rpcResult).toBe(12);  // Notice this is a number not a string

  // 5. Verify that storage is correct via RPC
  expect(await client.ctx.storage.kv.get('count')).toBe(12);
});

Let me know what you think or if you have any questions.

Usage | Lumenize

Doc-testing – Why do these examples look like tests?

LLarry I just released `@lumenize/testing` which builds on `cloudflare:test` vitest int...

1

1984 Ford Laser•10/16/25, 10:30 PM

Glad to see the CORS support here! That was something I had just run into with

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin so this is a prefect time for the release. Will definitely take a look

11984 Ford Laser Glad to see the CORS support here! That was something I had just run into with `...

L

Larry•10/16/25, 10:38 PM

You can use my

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin package with my advanced CORS supporting

routeDORequest

routeDORequest

routeDORequest

routeDORequest. I recommend the whitelist approach. See: https://lumenize.com/docs/utils/route-do-request#cors-support

However, the latest version of

routeAgentRequest

routeAgentRequest

routeAgentRequest

routeAgentRequest which is what

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin shows using in the docs has all or nothing CORS support. The third parameter is a config object and

{ cors: true }

{ cors: true }

{ cors: true }

{ cors: true } will allow all cross origins.

Request Routing | Lumenize

Route HTTP and WebSocket requests to Durable Objects with authentication hooks

LLarry You can use my `json-rpc-mixin` package with my advanced CORS supporting `routeD...

1

1984 Ford Laser•10/16/25, 10:40 PM

I plan to move entirely off of

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin and onto

lumenize

lumenize

lumenize

lumenize anyway so that I can remove the

agents

agents

agents

agents dependency, but good to know

LLarry I just released `@lumenize/testing` which builds on `cloudflare:test` vitest int...

L

lambrospetrouOP•10/17/25, 5:41 AM

Congrats on the release! Docs are looking good. Will try it out soon for my projects too.

Mmvgrim Also, seems like the Data Studio doesn't expose KV store data that is backed by ...

V

Vy•10/17/25, 3:34 PM

We have more work to expose KV data as read-only. Good to know there's a want here

P

PhoenixSpace•10/17/25, 7:33 PM

Is there any publicly available benchmarks on durable object size vs startup time? I'm storing a lot of data in durable objects transiently (~30gb, will be sharded over multiple obviously), and latency is a concern. Sharding isn't a big deal, but I don't want to pre-emptively overshard for no reason.

LLarry I just released `@lumenize/testing` which builds on `cloudflare:test` vitest int...

X

xormask•10/17/25, 9:53 PM

This looks awesome. Is the setup for using this in a multi-worker situation the same as with the vitest integration? (Precompile typescript to JS and then manually configure the secondary workers with miniflare?)

VVy We have more work to expose KV data as read-only. Good to know there's a want he...

1

1984 Ford Laser•10/17/25, 11:01 PM

I would totally use this too

LLarry You can use my `json-rpc-mixin` package with my advanced CORS supporting `routeD...

1

1984 Ford Laser•10/17/25, 11:02 PM

So I realised that this behaviour with CORS in the

agents

agents

agents

agents SDK isn't documented anywhere in the docs except for the changelog where it was introduced

11984 Ford Laser So I realised that this behaviour with CORS in the `agents` SDK isn't documented...

L

Larry•10/17/25, 11:37 PM

That's one of the problems with

agents

agents

agents

agents. The team has traditionally not consider docs (or quality, responsiveness on Discord, etc.) important although they say they are working on improving them. Also, it must be said that they have always had a great API design, even if you have to crawl in the code to discern it.

I have crawled around in their code and my docs on how CORS behavior works

{ cors: false}

{ cors: false}

{ cors: false}

{ cors: false} default and

{ cors: true }

{ cors: true }

{ cors: true }

{ cors: true } allow everything, are accurate for routeAgentRequest but I recommend strongly against using if you are using WebSockets. They don't support the whitelist or custom validation function modes that mine does.

E

Elijah Bowie•10/18/25, 3:23 PM

Has anyone successfully been able to use Sandbox? https://sandbox.cloudflare.com/

Been up all night.

Issue: Sandbox Sandbox SDK returning placeholder mode despite correct configuration
"Agent provisioned in placeholder mode (Cloudflare Sandbox API not configured)."

When my worker calls Sandbox.create it falls back to “placeholder mode” because the binding isn’t populated (runtime logs show Agent provisioned in placeholder mode (Cloudflare Sandbox API not configured)). It looks like Containers access hasn’t been enabled on my account yet.

Sandbox SDK

Run sandboxed code environments on Cloudflare's edge network

S

SuperHelpflare•10/18/25, 3:30 PM

Please do not post your question in multiple channels/post it multiple times per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

J

jonast•10/18/25, 7:44 PM

i noticed that errors thrown from functions called across a workers RPC boundary don't contain the original stack trace (for example when calling a function on a durable object stub or a service binding)

the serialized error that crosses the RPC boundary only contains the error message but not the stack

i'd really like to retain the original stack trace. what's a good pattern for doing that? stuff the stack trace in the message? or could i throw a custom error with the stack trace serialized in a property? would that cross the RPC boundary?

and is there a place where i can intercept any errors thrown out of the RPC boundary from the callee's side?

N

Nico•10/19/25, 5:05 AM

I'm working on an app where I use DO per user model. Given the release of data studio, allowing the inspection of a DO's SQLite storage, is there a way to assure users that I CAN'T inspect the state of their DO's state? Basically, can I limit access to data studio?