HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cloudflare
workers-sdk
TypeScript2022–2026
cloudflare / workers-sdk

workers-sdk

⛅️ Home to Wrangler, the CLI for Cloudflare Workers®

8Distinct people
10Mentions
1Explicit recommenders
4.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

⛅️ Home to Wrangler, the CLI for Cloudflare Workers®

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

I love v8 isolates so far-- I'm building chat tooling with it When added to the "edge", it means they're (insanely) fast, obliterate cold-start problem (which is killer in chat…

valgaze used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2022-06-15 20:18:54 UTC to 2026-06-25 12:38:54 UTC.

01232022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC312

What Hacker News says

10 sources
D1 reliability has been bad in our experience. We've had queries hanging on their internal network layer for several seconds, sometimes double digits over extended periods (on the order of weeks). Recently I've seen a few times plain network exceptions - again, these are internal between their worker and the D1 hosts. And many of the hung queries wouldn't even show up under traces in their observability dashboard so unless you have your own timeout detection you wouldn't even know things are not working. It was hard to get someone on their side to take a look and actually acknowledge and understand the problem. But even without network issues that have plagued it I would hesitate to build anything for production on it because it can't even do transactions and the product manager for D1 openly stated they wont implement them [0]. Your only
Read the rest
way to ensure data consistency is to use a Durable Object which comes with its own costs and tradeoffs. https://github.com/cloudflare/workers-sdk/issues/2733#issuec... The basic idea of D1 is great. I just don't trust the implementation. For a hobby project it's a neat product for sure.
In Cloudflare's AI Platform: an inference layer designed for agents
You can't really run the Worker code without modifications somewhere else afaik (unless you're using something like Hono with an adapter). And for most use cases, you're not going to be using Workers without KV, DO, etc. I've hit a bunch of issues and limitations with Wrangler and Workers locally over the years. Eg: https://github.com/cloudflare/workers-sdk/issues/2964 https://github.com/cloudflare/workerd/issues/1897
In Our container platform is in production. It has GPUs. Here's an early look
And what about the DX of using Workers with Pages? I tried to use that recently and it was a disaster. I wrote about my experience here: https://twitter.com/pierbover/status/1641474067013271552 I then opened these two issues: https://github.com/cloudflare/workers-sdk/issues/2962 https://github.com/cloudflare/workers-sdk/issues/2964 I ended up moving the project over to Netlify + Edge functions. I had it all working in like 5-10 mins as it should. Took me two hours to figure out why Workers weren't working in my Pages project, and could never get Workers working properly with my Astro project. I think you're working exclusively on the engine of Workers which is really top notch, but Cloudflare really needs to improve the outer layer which affects DX considerably.
In D1: Improvements to performance and scalability
> The fact that Apple itself relies on Linux for most of its servers is a pretty powerful heuristic that Linux is relatively safe [paraphrased by me] Many world-class companies depend on Windows, so does that mean you think Windows is safe? An individual does not have the same access to custom tools, and teams of competent people, that ensure their usage of the Linux ecology is secure. A recent example: I was investigating using CloudFlare Functions, because I think CloudFlare has world-class security and that “serverless” product avoids many security issues I might have with other solutions. Yet one setup step suggested piping in a script from curl to shell (commonly suggested for install steps!). Even worse, https://github.com/cloudflare/wrangler2 is their CLI tool to help development, and Wrangler is based on the node ecology, which is
Read the rest
completely insecurable as an individual developer IMHO (trillion dollar companies can probably secure the dev environment). I use a VM to provide some sandboxing, but it still leaves me feeling icky.
In Microsoft is phoning home the content of PowerPoint slides
valgaze·Jun 15, 2022Recommendation phrase
I love v8 isolates so far-- I'm building chat tooling with it When added to the "edge", it means they're (insanely) fast, obliterate cold-start problem (which is killer in chat where you might have not have retry), and as long as what you write can execute between 10-50ms (with ~30s for follow-on queries) it sometimes feels like cheating The same way Cloudflare "pushes" configuration to their network, they use a similar mechanism to push code to their edge nodes. They have killer dev tooling too-- https://github.com/cloudflare/wrangler2 You *DON'T* need to think about regions ever-- just deploy to a lot of small regions instantly & it usually "just works" and is fast everywhere. For extra credit, you also get access to rough-grained location information from each "node" in their network that your users connect to (globally you can get acc
Read the rest
ess to rough-grained local timezone, country, city, zipcode, etc): https://blog.cloudflare.com/location-based-personalization-u... ex. for chat, could so something like to prompt for location info: https://i.imgur.com/0qTt1Qd.gif Kenton Varda (https://twitter.com/KentonVarda) who was in charge of Protobuf and other projects gave an overview tech talk @ 10:23 speaks to isolates: https://youtu.be/HK04UxENH10?t=625 ## Downsides encountered so far - Not 1-1 replacement, think of your code like a highly-performant service worker (usual suspects: https://developer.mozilla.org/en-US/docs/Web/API/Service_Wor...) - Many libraries (like Axios for instance) won't work since they call out to Nodejs (this might be a good thing, there are so many web APIs available I was able to write a zero-dependency lib pretty easily) They're adding bespoke support for packages: https://blog.cloudflare.com/node-js-support-cloudflare-worke... - There's only a tiny of bit of customization for Workers required, however, there's a bit of platform risk If you haven't tried before, definitely worthy of further examination Re: security, it seems like a pretty good model.
In Ask HN: Pros and cons of V8 isolates?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.