INo. Eval is prohibited on all Workers, even WfP.
IWhat you can do on WfP is upload a Worker via the API and then run it from your dispatch Worker - so kind of like a slower eval.
DSo make a new workers per script?
IYes, a new Worker on Workers for Platforms.
D:rip:
IThe idea with WfP is you can deploy many many Workers (the usual limit of 100 doesn't apply)
D@Isaac McFadyen | YYZ01, EWR01 do you know if you can reset/have fresh context on every worker execution
Dfor example
Di make a global
Di dont want that global to exist on the next exeuction
Dfresh context
IIn general you shouldn't be using globals for this reason... what do you need a fresh context for?
Dso like sandbox
IAs in, you are running user code and the user code might store a global?
Dmy codebase uses globals
Dand i cant port it over to be localized
Di want fresh init each time
Di think workers cached it last time i tested
IAs far as I know this is not possible. Creating a whole new global state is quite expensive (relatively speaking), so Workers tries to minimize it as much as possible by not resetting global state every request.
Droger that
RHas anyone run into an issue where they use RPC https://developers.cloudflare.com/workers/runtime-apis/rpc/ and everything works as expected, but the logs for the RPC worker report an outcome of
canceled ? Also reported here but with no answers https://community.cloudflare.com/t/outcome-canceled-with-status-of-200-is-this-dangerous/653874 (context - I am calling an RPC worker from a user worker).Cloudflare Docs
The built-in, JavaScript-native RPC system built into Workers and Durable Objects.
PI really like the improved WFP UI on the dashboard
PI think if possible, it would be great to have more stats next to each worker in the list, like amount of requests, cpu time, etc
Pmight be on the list already, but quick edit would also be nice
DWould it be possible to update workers-for-platforms dev branch with the latest main? I'm missing the module aliasing feature which got added later.
DAny ideas why a service binding for a worker deployed to a dispatch namespace won't work when the script is deployed via an API, while the same binding will work when deploying with wrangler?
This one works:
This one doesn't:
In the second case,
The second worker is deployed to the dispatch namespace using this api: https://developers.cloudflare.com/api/operations/namespace-worker-script-upload-worker-module
This one works:
This one doesn't:
In the second case,
env.DATA_SERVICE appears to be an empty object with no methods.DataServiceEntryPoint is defined in the edge worker like this:The second worker is deployed to the dispatch namespace using this api: https://developers.cloudflare.com/api/operations/namespace-worker-script-upload-worker-module
Interact with Cloudflare's products and services via the Cloudflare API
JHey All,
Is it possible to use worker from ourside of the cloudflare zone?
Like CNAME the worker sub-domain from Go-Daddy?
Is it possible to use worker from ourside of the cloudflare zone?
Like CNAME the worker sub-domain from Go-Daddy?
Euse Cloudflare for SaaS to add a custom hostname and then run a worker route on that hostname
TIs there a limit in how many dispatch workers I can attach to a single namespace?
My goal is to give every customer their own subdomain and attach a dispatcher with access to the customer d1 and queue.
My goal is to give every customer their own subdomain and attach a dispatcher with access to the customer d1 and queue.
Wyou should really only need 1 dispatch worker
Wyou're giving the dispatcher d1/queue not the user worker?
Wbut no, there's no limit
TI see. I can have a single dispatch worker and have for each customer a user worker ready. Each user worker has access to the customer resources.
Cis Vercel edge using platform workers ?
Thyper
Vercel has created a zero config serverless platform, by adding files in an api folder you create api endpoints, no need for a server framework or listen to port command, you just need to bring your functions. 
Deno is the new typescript/javascript runtime from the NodeJS creator Ryan Dahl.
Deno is the new typescript/javascript runtime from the NodeJS creator Ryan Dahl.IThey use Cloudflare, it's not really publicized outside of a couple HN posts from people at Vercel though. https://news.ycombinator.com/item?id=29003514
leerob
Vercel's Edge Functions are built on top of Cloudflare Workers. The runtime is designed for any similar provider, but we've chosen Cloudflare for now because they have an amazing product.
Hacker News
•10/26/21, 5:41 PM
IRegular functions (non-Edge) use AWS Lambda.
JI'm having trouble getting my user-uploaded scripts registered as a queue consumer. Each script defines a
However, when I check on the queue in the dashboard, it says "No consumer". The queue producer is present, however. what could I be missing? in my case, the producer and consumer are defined in the same user worker
queue() method, which I've confirmed I've done correctly by hitting the Worker Details endpoint: However, when I check on the queue in the dashboard, it says "No consumer". The queue producer is present, however. what could I be missing? in my case, the producer and consumer are defined in the same user worker
Jah, just found this comment. are there any roadmap plans to let user workers act as queue consumers? would unlock some really powerful workflows! thanks! cc @tanushree │ Workers PM
AThere’s been no movement on this afaik. I’d suggest opening an issue on the workers-sdk git so the cloudflare team have more visibility of this being something we want
C- In order for me to link a customers domain, and provide traffic through workers for platforms, do I need to link the customers domain via cloudflare for saas, meaning I have to pay per month for each domain linked?
- Does workers for platforms allow me to link a customers root domain (without www.)?
P- Yes. It costs $0.10 a month per hostname with 100 included for free. To hook them up to workers you need to set the fallback origin to a proxied DNS entry (See more details)
- Yes you can do that too.
Cthank you!
EIts $0.10/hostname after 100 included, NOT $2 (cc @cake)
C$2 is the old pricing which was changed in 2022
Dseks
PThanks for the correction!
Eand that old pricing didnt have 100 included for free, so what was mentioned is a weird combination of both
