HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cloudflare
wrangler-legacy
Rust2019–2022
cloudflare / wrangler-legacy · Archived

wrangler-legacy

🤠 Home to Wrangler v1 (deprecated)

10Distinct people
10Mentions
0Explicit recommenders
3.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🤠 Home to Wrangler v1 (deprecated)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 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: 2019-03-28 19:08:19 UTC to 2022-05-19 12:05:04 UTC.

012342019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022

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
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202

What Hacker News says

4 sources
Not affiliated with Deno or Denoflare, but you can try Deno Deploy today! See https://deno.com/deploy/. Here's a recent status update from the blog: https://deno.com/blog/deploy-beta3/ Denoflare looks like a way to develop Cloudflare Workers locally, possibly as an alternative to Cloudflare's Wrangler CLI [0]. The Wrangler CLI has `wrangler dev` that serves a similar purpose by actually uploading local code to Cloudflare to run in the "real" Workers environment. Denoflare instead emulates it locally using Deno, given that both Workers and Deno provide Web Platform APIs. There's also Miniflare [1], which emulates a large portion of the Cloudflare Workers runtime and adjacent services like Durable Objects and the Key/Value store locally. Miniflare was recently promoted to an official Cloudflare Workers project [2]. [0] https://github.com/cl
Read the rest
In Denoflare – develop, test, and deploy Cloudflare workers with Deno
Here are things I ran into. `wrangler login` doesn't work if I'm not already logged in to CloudFlare website. If I have to login first, it doesn't do whatever necessary redirect it should do so most of the time I have to run `wrangler login` twice. `wrangler dev` is slow. `wrangler dev` requires root domain. https://github.com/cloudflare/wrangler/issues/1529 I also feel that the interaction between DNS settings and workers is under-documented, probably because it crosses responsibility of two different teams. For example, it took me way too long to figure out that if I have a workers-only website for foo.bar.org, I have to put dummy DNS entry for foo.bar.org Frankly, despite reading wrangler docs multiple times, I don't think I fully understand the interactions between what's in the DNS, what's in the workers route and further more if you
Read the rest
add pages to the mix. Docs should explicitly spell out DNS / routes setup for most common scenarios like: 1) workers-only site (no proxying to any other server) 2) workers in front of a proxied website Workers should be seamlessly integrated with pages i.e. pages should just automatically recognize and use workers-site/ directory on deploy. I don't think setting up pages automatically configures DNS settings for its domain, which it obviously should (might be mis-remembering).
In Miniflare – Simulator for developing and testing Cloudflare Workers
For example, wrangler dev just stopped working on all my current workers. All requests return a timeout error. Only workers created with wrangler generate work. I opened this issue and never received an answer: https://github.com/cloudflare/wrangler/issues/2077 I closed it because wrangler dev still works with generate, so I assumed it was a problem on my end. It still sucks that it just stopped working for no reason.
In Miniflare – Simulator for developing and testing Cloudflare Workers

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.