What JS framework has best support for Cloudflare Pages?
What JS framework has best support for Cloudflare Pages?
Vprobably Sveltekit or Next.js
DIt seems like svelte doesn't support live reload https://kit.svelte.dev/docs/adapter-cloudflare#bindings-testing-locally
Vnext.js supports fast refresh which I believe is what you're looking for https://nextjs.org/docs/architecture/fast-refresh
DI'm looking for fast refresh with support for Cloudflare Workers
envI was using solid-start up until now, but I couldn't get service bindings to work, presumably because it doesn't use wrangler, so miniflare doesn't see my other worker running.
DOr should I not expect this to be a thing?
HThere was some talk about it during the last Wrangler Office hours, but currently there isn't really a standard for runtime dev with
wranglerThat would only work if you could get the Next/SvelteKit builder to output the Functions script on every reload, no?
Vyeah maybe, not sure
DI mean, solid-start has that (they have live-reload but not with wrangler). Although If I understand correctly it is only because their adapter is still on Miniflare v2 (Miniflare v3 breaks many things).
DAlso this is MIniflare v2, which is (if I understand correctly) no longer supported. Miniflare v3 doesn't even have CLI.
HYes. With
v3 and onwards, you should use wranglerYeah, but this way there is no live reload.
DI found that service bindings don't work on Pages at all.
RAnyone ever tried deploying a SPA in a subdirectory with pages? I have an SSG for my landing page, and I want to serve my react app from /App. This works using "npx serve build", but not w/ cloudflare
Sdid you update the output directory in Cloudflare?
SUnder settings > Build and Deployments > Build Configs - edit root directory
RI actually think I figured it out. I thought that dropping my react app in /App would work, but instead I added a rename and copy command to my build script to rename index.html to app.html
BFor those who use Pagefind to provide site search, note that Pagefind 1.0.0 has been released with one breaking change:
https://pagefind.app/docs/v1-migration/
https://pagefind.app/docs/v1-migration/
RI have a pages app deployed to supplier-portal-fe.pages.dev and have added a custom domain s2.onthegotours.com . But there is something strange whereby s2.onthegotours.com is loading the content of www.onthegotours.com (our main website) instead of the pages site. Could there be something obvious I'm missing in this scenario?
RThe CloudFlare online chat support person suggested I change the 'target' field of the cname record from supplier-portal-fe.pages.dev to s2.supplier-portal-fe.pages.dev, which I did.. but that doesn't seem right to me.
HWhat is serving your
wwwPartially served by Cloudflare and partially on AWS
ZThat indeed seems odd... Did they mention why they recommend that?
RThey referred to this document - https://developers.cloudflare.com/pages/how-to/custom-branch-aliases/ But that's related to branches.. and I am just deplying the main branch at the moment
ZDid you add the subdomain under Custom Domains on the pages project?
R
RI'm not 100% sure on that, but I can try unproxying it. That record was how the pages interface created it for me
RYep, am removing now
ROk, great, it's working thanks!
RNot sure why it was proxied ..
RNow it's working I don't need to touch it 
Rthanks for the assistance
NI am trying to deploy in pages, but for some reason nodejs install is getting hanged. It's been 11 minuts and still nothing.
NIt's been happening for the last couple of days
NLast time it ran for 36m 36s but still couldn't download the node version.
NDoes anybody know why it's happening?
CThis happens occasionally where node takes a while to download from the site . If you are on build image v2 then you can try using a different version which is cached but I forget what versions are saved. Maybe try using v18
Nokay.
NThanks for the hint.
NWill check
N
K- would likely be pointed towards to using Wrangler to upload the assets from your own CI
KHello Cloudflare Community!
We need your help and hints on solving our case. The initial conditions are:
-- Account B: here is another project hosted, which we can’t move to account A, meaning we don’t wanna move it to another github org. (let’s call it project.com)
P.S.: Please, let me know if this message should go to another place.
We need your help and hints on solving our case. The initial conditions are:
- Two Cloudflare accounts:
-- Account B: here is another project hosted, which we can’t move to account A, meaning we don’t wanna move it to another github org. (let’s call it project.com)
- The project.com has multiple deployments: production, staging and another, which serves it’s content into subdirectory:-- Production: prod.project.com-- Staging: staging.project.com-- Subdirectory: subdir.project.com/subdir
- project-prod.siteA.com -> prod.project.com
- project-staging.siteA.com -> staging.project.com
- project-subdir.siteA.com/subdir -> subdir.project.com/subdir
P.S.: Please, let me know if this message should go to another place.
VHey Pages devs
, for those who don't know, you can sign up for Pages Build Cache Beta testing filling out this form https://forms.gle/2rQ8FCTtn2CUqmpk9 It currently supports Next.js, Gatsby and Astro, you can ask questions and share your feedback in build-caching-beta
, for those who don't know, you can sign up for Pages Build Cache Beta testing filling out this form https://forms.gle/2rQ8FCTtn2CUqmpk9 It currently supports Next.js, Gatsby and Astro, you can ask questions and share your feedback in build-caching-betaGoogle Docs
Pages is excited to introduce build cache - a feature designed to speed up your build times by caching and reusing previously computed project dependencies and build outputs. 
This is a very early version of the feature, and while we're excited about its potential, we recommend not enabling it on critical projects just yet. Please note that...
Pages is excited to introduce build cache - a feature designed to speed up your build times by caching and reusing previously computed project dependencies and build outputs. This is a very early version of the feature, and while we're excited about its potential, we recommend not enabling it on critical projects just yet. Please note that...
