I think I saw some types for DurableObjects somewhere (for TypeScript). Can no longer find them... did I dream?

Also, trying to export my TypeScript DurableObject "LogTopic" from index.ts. Using this syntax right now

export type { LogTopic}  from "./LogTopic"

But no joy...

"Cannot create binding for class LogTopic that is not exported by the script"

That's because part of your deployment script to CF Workers will be minifying the code. And part of that minification step will be renaming variable names, and in your case: class names.

Does anyone know why in

1.16

I can't call

--new-class

in

wrangler publish

?

Is there a correct way to get the name of the DO then from inside the DO?

is it possible to use DOs with typescript at the moment?

Im assuming by that you just mean are there typings. In which case yes there is from

@cloudflare/workers-types

more like in how to set it up. we're using the default webpack at the moment. from searching this channel i assume we have to migrate to rollup to get it to work?

You can find them in https://github.com/cloudflare/workers-types (e.g. https://github.com/cloudflare/workers-types/blob/master/index.d.ts#L676) There is no type for WebSocketPair yet. An issue has already been opened under https://github.com/cloudflare/workers-types/issues/84.

This is actually a bug in my code related to the magical realm of OOP and

this

pointers. the

this

pointer inside a lambda/anonfunc seems to be thrown off.

it seems the only way I can make the DO be aware of the name it has is by passing in the name with the worker fetch in the path?

seems kinda broken

i can get the internal ID no problem tho but its a hex string

Yeah this looks like a bug in our implementation. The standard says the arguments are optional, but apparently I didn't implement it that way.

I will try to get that fixed

Yes, you need to track the name separately. The system doesn't actually track the name. When you run

idFromName(name)

, you get an ID back, and the system doesn't remember the original name anywhere... it's basically a hash.

I've implemented a fix to make close() arguments optional. It should roll out next week.

still struggling with this... I took a look at my rollup output - a .mjs file that ends as follows:

export default g;
export { h as LogTopic };

Where

h

is the Durable Object class. But still getting that error:

"Cannot create binding for class LogTopic that is not exported by the script"

any ideas?

@User the rollup output is declared as the main module in

wrangler.toml

right? that syntax looks correct

you need to be using 1.16.0-durable-objects-rc.0, install instructions are on the wrangler github releases page

got it, if the DO is spun up, is the cost of resolving the name close to the same as using the ID? because I have DOs calling DOs, and i just got to thinking once I am inside the DO i can pass the id of the DO to the callee so the callee can call it back at a later time

right now i am passing the unique name (that is their userid basically)

yep - the module was also publishing fine until I added DurableObjects.

@User got a repo link?

let me upload now

only bug I could find is

main

should be just

./index.mjs

the path is relative from

upload.dir

(which defaults to dist)

I can't replicate the error message you're getting, if you change that does it fix it?

@User ^ (forgot to tag)