CI doubt Cloudflare is going to use something that isn't standard. Why would you want to proxy requests in the first place?
Sthere are lots of reasons we do it, but it's a pain. one example is integrating with a third-party service and needing a fixed IP
Sthere's already a cf object on fetch so...
CFair
Sthat screenshot is from Bun btw, lots of people are upset they added that 
CYeah bun is making some interesting choices
UBun will be its own thing no point in tripping over what they do 
but yeah I don’t really see cloudflare adding that. You can just setup the proxy server you make to accept the options of a request in a post pretty sure that’s at least the normal way of doing proxies
but yeah I don’t really see cloudflare adding that. You can just setup the proxy server you make to accept the options of a request in a post pretty sure that’s at least the normal way of doing proxies
SHi guys. I want to enable nodejs compat for worker via cloudfare dashboard. But there was no such "function tab" as specified in the doc.
S
SI think you can just add the following to your wrangler.toml file:
https://developers.cloudflare.com/workers/runtime-apis/nodejs/#enable-nodejs-with-workers
https://developers.cloudflare.com/workers/runtime-apis/nodejs/#enable-nodejs-with-workers
SI created my application using template. There is no wrangler.toml file in the src. Can you suggest how to do it via dashboard?
BFunctions are for Cloudflare Pages projects not for Workers
AThe new chart with 1 line per version is so satisfying. Thanks for this!
ARandom Q: I think the answer is no, but are there egress charges for Workers? I've been reading https://www.cloudflare.com/en-gb/learning/cloud/what-are-data-egress-fees/
- https://developers.cloudflare.com/workers/platform/pricing/ and there's no mention about workers. It focusses on R2, but in the pricing, there's nothing about egress - just requests/CPU etc. so while it doesn't explicitly say, is there anywhere that explicitly says in the docs/website (and Pages too as a bonus!)
HThere are no egress fees, no
AI thought not, it seems weird Cloudflare doesn't shout about it more, and only talks about R2? Like, even just saying "no egress charges" under Workers pricing would make sense 
Unless I am just blind. Is it fair to say there are zero egress charges for any Cloudflare developer products?
Unless I am just blind. Is it fair to say there are zero egress charges for any Cloudflare developer products?Aty
CIs there anywhere to see recent worker releases etc? My worker has started to do weird things with the cache API (things aren't caching as long as I would have expected) and I've not touched that code in some time.
Chttps://developers.cloudflare.com/workers/platform/changelog/
cache APIAssets in cache are evicted based on access frequency, it's possible they changed some internal cache stuff too and I don't think that would be in the Workers change log at all. As long as they being put in cache and serving HITs (the cache api is actually working), then the rest is up to the cache service
CShort of pinging a ticket into my AM there isn't anyway for me to know if something has changed in the cache service I imagine?
SI have an API that I am calling in my worker, which requires my IP address to be whitelisted to access. How would I get the IPv4 address of my worker once it is deployed so the API can be accessed in the worker?
IYou cannot. Workers run on every machine in the Cloudflare network and so use many different IP addresses.
AHi all,
I’m kinda new to JS backends and serverless in general. I’ve recently followed this tutorial (https://youtu.be/H7Qe96fqg1M?si=dtk0DoiFW275Fc20) and had a mostly pleasant experience.
I’m wondering now how would I build a larger backend to power an API with Cloudflare workers. If I wanted to have multiple workers responding to different paths like controller endpoints, what’s the “recommended” way to achieve that? I’m trying to assess feasibility of using this toolchain more deeply in building products and want to make sure I understand its use cases and how to do basic things before I commit too much time to learning it
I’m kinda new to JS backends and serverless in general. I’ve recently followed this tutorial (https://youtu.be/H7Qe96fqg1M?si=dtk0DoiFW275Fc20) and had a mostly pleasant experience.
I’m wondering now how would I build a larger backend to power an API with Cloudflare workers. If I wanted to have multiple workers responding to different paths like controller endpoints, what’s the “recommended” way to achieve that? I’m trying to assess feasibility of using this toolchain more deeply in building products and want to make sure I understand its use cases and how to do basic things before I commit too much time to learning it
YouTubeCloudflare Workers
Learn how to build your first Cloudflare Workers application and deploy it to Cloudflare's global network. If you don’t already have an account sign up for a free Workers account today! https://workers.cloudflare.com
Hosted by Kristian Freeman, Cloudflare Developer Advocate
https://twitter.com/kristianf_
Get Started guide for Cloudfla...
Hosted by Kristian Freeman, Cloudflare Developer Advocate https://twitter.com/kristianf_ Get Started guide for Cloudfla...
CHey all, I am exploring service bindings right now, and the docs state one advantage of service bindings is:
https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/
However, I can't find any instructions on how to achieve this - my assumption being that this is only true if you use the RPC interface, rather than the HTTP interface. Is that true? and if that is the case, I guess it is less clear to me what the advantage of setting up a service binding for a http interfaced worker. Thanks in advance for the help!
Isolate services from the public Internet. You can deploy a Worker that is not reachable via the public Internet, and can only be reached via an explicit Service binding that another Worker declares.
https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/
However, I can't find any instructions on how to achieve this - my assumption being that this is only true if you use the RPC interface, rather than the HTTP interface. Is that true? and if that is the case, I guess it is less clear to me what the advantage of setting up a service binding for a http interfaced worker. Thanks in advance for the help!
Cloudflare Docs
Facilitate Worker-to-Worker communication.
HNo, it applies to both. If your Worker exports a fetch method, then it is available via the Service Binding
CYep, that is correct, however I can't figure out how to have a worker only be triggered via a service worker, and not open to public http requests
HDisable workers.dev, don’t have any routes, or a Custom Domain
CGreat! thanks
CFor
@wrangler-action
EGuys, regarding Workers <> Neon
What's more performant,
What's more performant,
- utilizing the "prebuilt" way of connecting (think it uses websocket to connect to a neon proxy)
- utilizing raw TCP connection to it via hyperdrive
?
ESince websocket also needs tcp in the beginning I'd imagine the hyperdrive way of doing things to be better
MMaybe a dumb question, but for my worker development environment hosted on *.workers.dev, is it possible to remove my email from the domain (it get's added on by default).
Found the solution, I can change the subdomain
Found the solution, I can change the subdomain
Summ where do i post query about email workers?
H#email-routing
Sthankyou, have raised it there
V@HardlyWorkin'
H?pings
FPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
AHey everybody,
Is the
Is the
request.signalrequest.signal.addEventListener("abort" ()=>{})
LI saw the Workers changes and I'm wondering whats up with the Worker to Worker RPC Pricing reduction? Didn't a cloudflare employee say it'll come soon?
URPC hasnt even been out for a month yet "soon" in cf talk generally means at least a few months
UAnd fwiw worker requests are only 30 cents for a million requests even doing like 10 rpc calls is still a crazy good deal
Lreferring to this post. didn't quite make it this weak doesn't sound like months https://twitter.com/irvinebroque/status/1776331933129253290
@sperand_io @elithrar @Cloudflare Two things here:
- We are working on (couldn't quite make it for this week) a change where when you call another Worker via a service binding, this won't be billed as a request. (so that pricing doesn't disincentivize breaking apart an app into many Workers) Coming soon.
4/5/24, 7:31 PM
UI’m aware of the post but still it will probably be a few months for that to be added
