Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wrangler 2.0 – a new developer experience for Cloudflare Workers

blog.cloudflare.com

Post reply on HN
Print view View original

1–8 of 8 posts

Re: Wrangler 2.0 – a new developer experience for Cloudflare Workers

#4

Post by threepointone »

lucasyvas wrote: post #3

I'd be curious to know how language decisions are made for this tool. I notice Wrangler v1 is Rust, and now this has flipped back to JS/TS. Was the motivation largely driven by Miniflare, which is based on Node? Nice feature set though!

Hello! I'm on the team that implemented this. I'll be writing a longer post on the design considerations and implementation details, but roughly - rust wasn't a good case for something that was mostly held back by i/o to the edge; further, the actual cpu/mem intensive part was handed off to webpack which was written in javascript. So wrangler v2 flips that design around, using typescript for the outer shell, which makes it easier for our users and community to contribute to the tool, and esbuild for the core part of parsing/bundling code (we may switch esbuild to a rust based bundler like swc in the future).

Re: Wrangler 2.0 – a new developer experience for Cloudflare Workers

#5

Post by VTimofeenko »

KuiN wrote: post #2

I love the idea of Cloudflare workers & really want to play with them in some spare time, but I've not really got any idea what I could actually _do_ with them ... What are people using CF Workers for? Any interesting use cases?

At $DAYJOB I need to set up demos of a system that provides a dynamic UI to provision various products. The system can emit webhooks for validation of incoming parameters (email, address, etc). With CF workers and almost zero prior knowledge of JS I was able to set up a working validation endpoint in about an hour.

CF provides a very neat way to route requests to subdomains to specific workers and terminates SSL, which was perfect for my use-case.

Re: Wrangler 2.0 – a new developer experience for Cloudflare Workers

#6

Post by lucasyvas »

threepointone wrote: post #4
lucasyvas wrote: post #3

I'd be curious to know how language decisions are made for this tool. I notice Wrangler v1 is Rust, and now this has flipped back to JS/TS. Was the motivation largely driven by Miniflare, which is based on Node? Nice feature set though!

Hello! I'm on the team that implemented this. I'll be writing a longer post on the design considerations and implementation details, but roughly - rust wasn't a good case for something that was mostly held back by i/o to the edge; further, the actual cpu/mem intensive part was handed off to webpack which was written in javascript. So wrangler v2 flips that design around, using typescript for the outer shell, which ma…

Thanks for the background!

Re: Wrangler 2.0 – a new developer experience for Cloudflare Workers

#7

Post by dsvepitt »

KuiN wrote: post #2

I love the idea of Cloudflare workers & really want to play with them in some spare time, but I've not really got any idea what I could actually _do_ with them ... What are people using CF Workers for? Any interesting use cases?

https://developers.cloudflare.com/workers/examples

There are some examples there and also a section of built with Workers. (Random CF employee)

Post reply on HN