Are you using the new persistent logs (you'll have an [observability] section in your wrangler.toml
Are you using the new persistent logs (you'll have an [observability] section in your wrangler.toml if you do) or real-time logs?
AAnd where are you running your Worker?
NThere’s no observability section in my toml file so I don’t think so
NI have it currently in a folder on my desktop with the files for the web app I’m building
Aregarding your first item: adding check runs in github for Workers Builds is on our radar! we are working on it.
AAre you running it locally when you are trying to see logs (hitting localhost), or are you accessing a URL like something.workers.dev?
Nlocally
OAnyone able to create an app with the new Remix worker template? I tried following https://developers.cloudflare.com/workers/frameworks/framework-guides/remix/ but the app it made seems to still be using pages. eg, the deploy command it gives is
wrangler pages deployCloudflare Docs
Create a Remix application and deploy it to Cloudflare Workers with Workers Assets.
JI need myblogexample.pages.dev to be accessed by myblogexample.org but when I add the domain in the Pages settings, the message below appears
"After the update, visitors will no longer be able to access your site when visiting https://myblogexample.org."
I didn't understand
I want it to be accessed by myblogexample.org without displaying myblogexample.pages.dev
"After the update, visitors will no longer be able to access your site when visiting https://myblogexample.org."
I didn't understand
I want it to be accessed by myblogexample.org without displaying myblogexample.pages.dev
HIt sounds like you might already have a DNS Record for that domain? I think it is warning you that it would remove that DNS record
JYes
4 types:
R2 ( bucket )
CNAME ( www to myblogexample.org )
Worker ( subdomain.myblogexample.org )
Worker ( subdomainb.myblogexample.org )
4 types:
R2 ( bucket )
CNAME ( www to myblogexample.org )
Worker ( subdomain.myblogexample.org )
Worker ( subdomainb.myblogexample.org )
OYes, I'm saying the command in that doc
npm create cloudflare@latest my-remix-app -- --framework=remix --experimental
Rseems like still no mongo support?
VAnyone has ever had issues building telegram bot where the worker is not responding , or is but a while later ?
my previous bot was working fine but don't know what is wrong with that one ...
my previous bot was working fine but don't know what is wrong with that one ...
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.
AHey all, I just went through the process of migrating my Remix site to the new Workers static assets setup.
Things went pretty smoothly, however the one thing I couldn't find a solution for is how to set the
In pages, we used to be able to have a
But that doesn't seem to work anymore.
What is the recommended way to do this now?
Things went pretty smoothly, however the one thing I couldn't find a solution for is how to set the
headersIn pages, we used to be able to have a
_headersBut that doesn't seem to work anymore.
What is the recommended way to do this now?
Cloudflare Docs
To attach headers to Cloudflare Pages responses, create a _headers plain text file in the output folder of your project. It is usually the folder that contains the deploy-ready HTML files and assets generated by the build, such as favicons. Changes to headers will be updated to your website at build time. Make sure you commit and push the file t...
HAfaik currently you would have to apply headers via a rule(or via the Worker itself)
AHmm I see. Ok, thanks for clarifying. I'll look into how to set the headers on the worker directly.
AAh, are you looking for the logs on the dashboard in the browser? As logs for locally-running apps will be displayed in your terminal (where you wrangler dev / npm run dev)
PHey @outsideurimagination - that create-cloudflare usage does actually create a Workers app, it's just that the npm "start" script has not been updated to Workers (it incorrectly still mentions Pages).
But you will not that the "deploy" and "preview" scripts do actually result in workers:
It is slightly confusing because it is indeed still using the Cloudflare Pages Remix adaptor (for the moment) which generates a Pages Function output, which then needs to be converted to a Worker via the call to
I hope to have a better template out soon
But you will not that the "deploy" and "preview" scripts do actually result in workers:
It is slightly confusing because it is indeed still using the Cloudflare Pages Remix adaptor (for the moment) which generates a Pages Function output, which then needs to be converted to a Worker via the call to
wrangler pages functions buildI hope to have a better template out soon
Ook thanks. I know they’re also updating the template in the remix repo. might check that out if you haven’t to not duplicate effort https://github.com/remix-run/remix/pull/10034
GitHub
This PR updates the cloudflare-workers template to use the Static Assets feature announced today.
Note: Static assets is currently in open beta
You can learn more about Static Assets in the docum...
Note: Static assets is currently in open beta
You can learn more about Static Assets in the docum...
FI'm trying to access Origin from a function, but it doesn't return anything. Is it possible to access the Origin of a request, if so, what am I doing wrong?
export async function onRequest(context) {
const origin = context.request.headers.get('Origin') || 'Not available';
...
}
export async function onRequest(context) {
const origin = context.request.headers.get('Origin') || 'Not available';
...
}
BAny 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
