Any issues with workers? `ctx` seems to be empty for us sometimes, since a couple of hours
Any issues with workers?
ctx
DI created a test worker, seems fine from a few colos that I tested
BSeems that something changed under the hood in workers - we did a check to see if ctx was a valid object somewhere in our code, and this started failing since a couple of hours. I guess a change in the latest workerd that Cloudflare started rolling out globally
Dcan you share the code for this check?
DI log the typeof ctx and the constructor.toString, and it looks correct, and identical across regions
BWe used a util that (among other things) checked for this under the hood - this is the part that failed
UHello everyone, I need help setting up multiple Shopify stores on a single .com domain using Cloudflare. The idea is to use Workers or Transform Rules to automatically switch between different Shopify subdomains at set intervals (e.g., 12 hours per store) for load balancing. The main domain should always mask the Shopify subdomains, with all routing done through Cloudflare, without any changes on Shopify's end. Each store will have the same content. How can I achieve this and is it even possible?
Dcould you share a little more so I can repro and escalate if it is actually a runtime change?
LHas anyone else seen a significant jump in bundle size when using a compatibility date >=
2024-09-23nodejs_compat
KThat's intentional -
nodejs_compatnodejs_compat_v2compatibility_dateYes, this crashes with
We think this might be the commit that caused the behaviour change: https://github.com/cloudflare/workerd/pull/2801/files
I assume impact will be low though, pretty niche to do this check on
"wrangler": "3.78.10"3.78.9We think this might be the commit that caused the behaviour change: https://github.com/cloudflare/workerd/pull/2801/files
I assume impact will be low though, pretty niche to do this check on
ctx
Dthat's because workers with nodejs_compat and a compat date that is newer than your date have some js polyfills added, in addition to the runtime compat mode that it enables
Dthanks, I'll forward this info
LGotcha, I thought unenv was supposed to be smart about adding polyfills. Thanks for the info!
BEven though we fixed our wrangler at 3.78.6, we were still impacted - it looked like there was a gradual rollout of a newer version throughout the day
Dit should only add what you might use
Dcorrect, that's usually how runtime releases are done, and your version of wrangler only affects your local runtime version
Bmakes sense
LI'm not using anything in the worker itself, just have it for vitest.
LI'm guessing that extra size is from boilerplate from unenv, or maybe it's coming from my tests?
Rhow many requests can a single worker handle? in AWS, GCloud and al., we see the concept of "quotas" and number of "container instances" spawned over time. We don't have such information on Cloudflare dashboard. Is it using a single worker for each request; or rather a single worker can handle millions or more requests by itself?
WThere is no limit, I've done over 100k rps myself from my own laptop and of course we do much more as a whole platform
Each Worker can handle tons and there could many many thousands of worker instances.
Workers are light and so can be created everywhere and handle a lot
Each Worker can handle tons and there could many many thousands of worker instances.
Workers are light and so can be created everywhere and handle a lot
Adoes snippets support kv? If not is there any plan to add this support?
AI wish workers has support for firebase sdk and mongodb. That's the only thing stopping me to deploy to workers. Currently have to use google cloud run for docker instance.
HWhy not D1 or KV
WSnippets have no bindings access. They're meant for lightweight use cases
WAnyone getting error with wrangler deploy command, I am latest version 3.79.0
workers.api.error.unknown [code: 10013]
WWhat's your account ID?
W9c508e2e1d1c6d075d774819cf38176c
I was using it with Cloudflare account token template settings by exposing it to environment but getting api errors, so I logged in with wrangler login and deployed. It worked that way
I was using it with Cloudflare account token template settings by exposing it to environment but getting api errors, so I logged in with wrangler login and deployed. It worked that way
Fis there any template for running remix spa mode in workers?
FIf the _headers file doesn't work anymore, would be good to remove it from the template, otherwise, it's a bit confusing.
IIt still works with Pages which is what the template is designed for AFAIK
THey w3b, we discovered a bug related to account owned tokens this morning. The team is looking into it, thanks!
Foh, i thought that
pnpm create cloudflare@latest web --framework=remix --experimentalApologies - you might be right 
Fhaha no problem
KIs there a way in a worker (js) to get the current version/deployment id?
CCloudflare Docs
Exposes Worker version metadata (
versionIDversionTag
AKV not good for everything and can't migrate. D1 is limited, no read replica, no sharding. Firebase I'm using only for firebase auth. And I'm using more node.js features (packages) that is not supported by even latest node_compat.
KHow do I define that in the toml across multiple env? It fails when trying to add the key to separate env and warns when it’s not in separate env. Latest wrangler
TCan you share your toml? I set it globally as defined in the docs and not getting any errors or warnings
KHere you go, redacted some info
wrangler.toml2.17KB
K
W[env.local.version_metadata]
WTOML is great :meowupsidedown:
Kah geeze, thanks! That sorted it 
Dhey, I think this is being addressed, there's a compatibility flag so if you're using something older than
no idea when it will be rolled out to prod, so could be that you're already back to the old functionality, or maybe only next week
2024-09-26no idea when it will be rolled out to prod, so could be that you're already back to the old functionality, or maybe only next week
WDani too fast, yes we're working on rolling out a fix gating this change now
