Cloudflare

`nodejs_compat` is in the runtime, so doesn't contribute to bundle size.

Does `nodejs_compat` require the experimental local to run?

Or better question, what's the feature parity % currently between both of them?

Removing `node_compat` and putting in `nodejs_compat` instead errors out on missing `util` and `os`.  ~~I assume both should not be enabled at the same time?~~ yea it won't even let me run with both

Ok, just tested with `experimental-local` on WSL Ubuntu 22 (node 18 + wrangler 2.13.0) and `util` and `os` still missing

I guess I'll wait and be on the lookout for when it's available so I can swap node compat options <:lul:946531054485930015>

Only parts of util are implemented, and `os` is not

are there any plans to support https://developer.mozilla.org/en-US/docs/Web/API/HTML_Sanitizer_API in the workers?

because all of the popular existing ones seem to be created for NodeJS and CF workers lean towards browser rather than the NodeJS

It seems like a pretty early on API but you can make a feature request on <https://github.com/cloudflare/workerd/issues> to have it considered

Sure,  message me when you're ready to share.

Anybody else seeing a `script body must not be empty (Code: 10021)` error when attempting to save an environment variable to a worker (via the web interface)? 

Status dashboard doesn't seem to indicate there's an ongoing issue: https://www.cloudflarestatus.com

This _isn't_ a new worker. It's been running for about a week, and it already has some other variables saved.

<@1052249953570918430>, might want to raise this? (tldr: adding env variables to a worker in the dash is erroring)

We just did a release of worker service earlier

do cron-triggered workers also have a limit on subrequests?

This is now resolved: https://www.cloudflarestatus.com/incidents/k06xyl212xfk

and, is there a way to use the unbound plan for cron triggered calls and the bundled plan for non-cron triggers?

Yes on the subrequest limit, no on the split plan, at least at the moment

ok, so i guess i just have to create separate workers then :)

thanks tho <:MeowHeartCloudflare:897193652089155645>

can a single worker have both a `fetch` handler and an `email` handler?

Is this the right way to set up a "match all" rule for rate limiting all my workers on that domain?