thanks

For workers (not DOs) with a websocket connection are they billed by the time the websocket is connected, or only the time processing messages?

From my understanding, the worker still has to be kept alive while a client is connected, so you'll be billed for the whole duration

Right now the whole time, but soon there will be an API to hibernate it

That'd only be for DOs though, right?

Probably, yes

Gotta check the docs

for the example of asynclocalstorage, that wouldn't work within a DO because the thread is shared, correct? Only works in the case of workers because the are dedicated thread per request?

Yeah I'd love to be able to just have websockets open that invoke a worker when a message goes through so that I can do a socket proxy to an api

without needing th eworker for the whole websocket, just the message

Regular Workers aren’t single thread per request, I don’t think

well I meant like they script context is not shared

IIUC

Globals are, iirc

Which is why SW syntax is so slow

sw?

Service Workers -

addEventListener

gotcha

yeah I don't use that lol

But yeah, the whole reason they added piped in env vars was so that they could modify them on request, rather than having to reboot the entire isolate first

makes sense, was just wishful hoping XD

It sounds like you want WebSocket hibernation with Durable Objects, based off this

but of course that's only a DO thing

Can we revisit this? Any way to detect IF crawler using cloudflare worker on PRO plan?

No I want it stateless, just a proxy for an api

How do you folks use Jest in your Workers?

I kinda want to expose a health check endpoint that uses Jest to test all the other endpoints.

hello, how to avoid

Unhandled Promise Rejection: Error: recursive use of an object detected which would lead to unsafe aliasing in rust

when using HTMLRewriter to append elements? This is the code that fails:

class SimilarWordsElementHandler {
    constructor(similarWords) {
        this.similarWords = similarWords;
    }
    async element(element) {
        element.setInnerContent(null);
        for (const similarWord of this.similarWords) {
            element.append(`<li>
                <a href='/word/${encodeURIComponent(similarWord)}'>
                    <span>${similarWord}</span>
                </a>
            </li>`, { html: true });
        }
    }
}

What's the difference between the

nodejs_compat

flag from today's post (https://blog.cloudflare.com/workers-node-js-asynclocalstorage/) and the

node_compat = true

flag that has been available all this time?

node_compat = true

is just polyfills in esbuild