Juho Vepsäläinen

@andywer Let me check the remaining ones. :)

@andywer It should be far better now in terms of formatting.

I was able to simplify the code somewhat based on your comments. I realized it's possible to reuse the existing `expose` without a factory. I added a bit of logic...

> Is there any way I can help? There is one issue: ```bash ~/threads.js  feat/shared-workers  npm run test:puppeteer:basic  ✔  system Node > [email protected] test:puppeteer:basic /threads.js >...

> I have been thinking about it on and off since yesterday, but that's also weird for me… I don't see how, but maybe the worker is somehow run as...

It seems it times out at `const initMessage = await withTimeout(receiveInitMessage(worker), timeout, ...` when spawning. I think it might be related to the way we're handling `expose` for shared workers....

It definitely seems that we're missing `onconnect`. I started sketching it out and there are some debug prints in place for now. If you have time, feel free to mess...

It turns out my client doesn't need the feature anymore (different approach now). @pubkey If you want to complete the work, that would be great.

I've been exploring functions within CF pages lately and I would definitely benefit from having denoflare available there as well. Right now I have to repackage my code so that...

Minimum - document how to achieve it outside of the cli. I guess it depends on the overall goals and priority. I expect v1 would be more or less what...