If the _headers file doesn't work anymore, would be good to remove it from the template, otherwise,
If 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 --experimental bootstrapped a workers projectIApologies - 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 (
versionID and versionTag). These fields can be added to events emitted from the Worker to send to downstream observability systems.
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-26 you should see the old behaviorno 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
Thmm, anyone know what the size limit is for workers static assets?
TShould be 25MiB
T(Same as pages)
Tah, so also built upon kv?
TYup!
A- yup, we will be adding that soon
- what do you mean by environments? do you mean Workers environments or something else?
Cloudflare Docs
Deploy the same Worker application with different configuration for each environment.
QDoes Workers Static Assets have the same 20k file count limit that Pages does?
LHow do you submit feature requests? You can only through a ticket on a business/enterprise plan? I could ask one of my clients, but I'd rather not bother them.
H#workers-feature-suggestions ?
ADNS and domains aren't my strong suit, so in the case where I want to allow custom domains, that are customer-owned (e.g. I do not own them, my customers do) to be tied to my worker... is the best way Workers for Platforms?
Or could I start out with something simpler / no upfront cost (e.g. a single worker with lots of routes tied to it)?
I know I can have quite a few routes associated to a worker (I think 1,000), it's more the DNS/zone side of things that I am curious about (do I add their domain to my account, then they repoint DNS?) and how it would work from a customer PoV / wanted to check if there was anything I was missing between the two choices.
Or could I start out with something simpler / no upfront cost (e.g. a single worker with lots of routes tied to it)?
I know I can have quite a few routes associated to a worker (I think 1,000), it's more the DNS/zone side of things that I am curious about (do I add their domain to my account, then they repoint DNS?) and how it would work from a customer PoV / wanted to check if there was anything I was missing between the two choices.
HYou need CF for SaaS to allow CNAMEing
HAssuming you don’t have custom logic per zone for your Worker, then you should be able to get away with just one
AAhhh it's hidden under the Workers for Platforms page That looks perfect, thank you. And my customers would just CNAME whatever they wanted to (e.g. customdomain.example.com) to my.worker.domain? (going with the easier-looking real-time option)
That looks perfect, thank you. And my customers would just CNAME whatever they wanted to (e.g. customdomain.example.com) to my.worker.domain? (going with the easier-looking real-time option)HYes, though note you also have to add
customdomain.example.com in the dash/via the APIAYup makes sense, thank you!
TYes it does!
QBummer.
T?crossposting
FPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.TAlso I don't think this is the place to advertise period - even offtopic - and you'll like get banned
T@Tim Bless
AIm sorry bro
IWorkers Builds don't use Workers to build (so not V8), they use Cloudchamber (Cloudflare's container platform): https://blog.cloudflare.com/container-platform-preview/
LOk, still from my tests it takes around 10s on average to start the build from when you queue a job.
LThat's very fast and on-par with GHA.
JHello!
Why this simple code not work? (internal endpoint)
The response
I trying with
Why this simple code not work? (internal endpoint)
The response
status_code=200 and {}, empty json.I trying with
npm run previewimport type { NextRequest } from 'next/server'
export const runtime = 'edge'
export async function GET(request: NextRequest) {
return Response.json({"a": 1});
}
PIs there plans to support
stale-while-revalidate and Vary header for other values?
MHey, I'm curious, how does sending email via Cloudflare works?
IYou can't. The only exception is if you use Email Routing, in which case you can only send email to your own (authorized) addresses and only in response to an existing email coming in.