AsyncLocalStorage on Cloudflare

[victormihalache]

I was looking at the deployment page for platform-specific instructions. It says that for serverless platforms I should set disableAsyncLocalStorage to false as it's not needed due to each request spawning a new instance, but immediately after it says that for Cloudflare one just has to add the nodejs_compat compatibility flag.

Isn't Cloudflare Pages (+ Workers) like serverless? as in: static assets are deployed on a CDN and dynamic routes are on the edge—which spawns a worker to render the page?

[samuelstroschein]

@LorisSigrist can you answer this one?

[LorisSigrist]

On Cloudflare you can do either. Either disable AsyncLocalStorage, or set nodejs_compat

[victormihalache]

What difference would it make?

[LorisSigrist]

Disabling AsyncLocalStorage might result in slightly better performance.

We should probably stop recommending nodejs_compat. The main reason it's in the docs is just that it predates the AsyncLocalStorage option.