Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Unless you go for Enterprise you can only have a single worker per site making QA and staging hell.

Their JavaScript environment/APIs are not standard and there’s no proper spec that I could find.

The debugging environment/IDE is decent for an in-browser one but we had some horrible issues with a stale version being loaded from local storage and accidentally applied to the entire site effectively bringing us down for several minutes.

On every change I also saw several error pages myself during warmup period which made me wonder how many customers were getting them.

This was all ~6 months ago though so things might have improved since then.

Performance wise we’re very happy with it though as it beats the Apache reverse proxy it replaces hands down.



They're using the Service Worker API: https://developer.mozilla.org/en-US/docs/Web/API/Service_Wor...

It's not running in a browser so they reimplemented some things but the overall API surface is the same. They also have some extra APIs for CF only features.

Debugging is a problem though, but there's another project called Cloudworker that emulates a local instance: https://blog.cloudflare.com/cloudworker-a-local-cloudflare-w...


(shameless, but possibly helpful plug)

You can run CF worker code locally, write tests, etc using our edge app runtime: https://github.com/superfly/fly




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: