Cloudflare Developers

CD

Cloudflare Developers

Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news

Join

Yeah it can with functions

Yeah it can with functions

https developers cloudflare com pages

https://developers.cloudflare.com/pages/framework-guides/deploy-a-qwik-site/#use-bindings-in-your-qwik-application The example in this section is incorrect, it should be: ```typescript export const useKVData = routeLoader$(({ platform }) => { // This is wrong:...

During the build process sorry if it

During the build process, sorry if it wasn't obvious before :p

Buffalo wild wings

Hi Everyone, as of this morning, Buffalo Wild Wings has joined Arby's and is now on Cloudflare Pages as of this morning. We've logged zero issues and it is snappier. Please feel free to ask questions if you have any and I will answer as much as I can....

Hi everyone we re exploring deploying

Hi everyone - we're exploring deploying our Remix app to CF Pages. We can't do the whole hook-up your repo and let CF do the magic because we're running a mono-repo with various projects in it, so we'd like to push it. I found somewhere that we can use wrangler, and wrangler is deploying the assets to the pages, but I must be missing something, because I see no workers defined and going to the preview URL gives me a 404.

Clerk sign out issue with next.js

Sometimes, cloudflare pages + next.js turns out to be quite bad. I am using clerk authenication and have a signout button. On click of signout, it should redirect to signin page, but cloudflare get stucked without any errors. On vercel same thing works fine. ...

Hi I have weird issue We are using

Hi, I have weird issue. We are using Cloudflare Pages, they are deployed from CI. We use preview domain aswell custom domains in our root domain. We have zero trust set for preview domain set and disabled it for dev and rc subdomains in our root domain. For some reason users are still redirected to preview Application to do Zero Trust login.

I have no idea what they do but it s

I have no idea what they do but it's probably the most common framework it happens with

Document how to use `adapter-cloudflare`...

https://github.com/sveltejs/kit/issues/2966 I've been reading through this and wondered if there was a solution yet? As I'm working on a SvelteKit pages project, that's using SSR (using a service binding) and naturally platform.env is undefined in dev... which makes local testing really difficult. Does anyone have a good solution (there are some in the issue but they are all quite hacky)

No this is something the Hugo folks have

No, this is something the Hugo folks have been trying to fix for a couple of years now but haven’t yet arrived at a solution that satisfies all their requirements. That’s why I was so excited about v2 including the Embedded Dart Sass binary. With the changes announced in the blog post, having the regular Dart Sass binary in the PATH now accomplishes the same thing. It’s just a matter of making sure to use that binary rather than the now-archived Embedded Dart Sass binary. @johndotawesome the difference between Hugo and Hugo Extended where Sass is concerned is that Hugo Extended supports the use of Sass, while “regular” Hugo (an oddity of the Hugo build process for a very small number of OS versions) does not. At one time, Hugo Extended did come with the old/deprecated Libsass, but it’s never included Embedded Dart Sass....

UX feedback bug When pasting an

UX feedback/bug: When pasting an environment variable in the format FOO="bar" you have to "blur" the input field before it is actually inserted into the form field, rather than a keydown/paste event firing it. This makes it feel broken when putting in env vars into Pages

@cloudflare/[email protected]

Hi! We released @cloudflare/[email protected] earlier today which caught some people out — apologies if you were affected by the breaking change. We've tagged the latest 0.X release (@cloudflare/[email protected]) as latest again so that, if you are relying on the implicit npx @cloudflare/next-on-pages build command, you'll pull that version and hopefully will be back to a good state. Going forward, we're going to migrate everyone who has an implicit npx @cloudflare/next-on-pages build command to npx @cloudflare/next-on-pages@pre-v1 . This will keep them on the 0.X releases. We'll, only then, point latest back at the 1.X releases. The framework preset in the dashboard will be updated to npx @cloudflare/next-on-pages@1 so new projects will be using the newer versions by default. Apologies once again for the inconvenience and confusion. We're also going to be recommending you install @cloudflare/next-on-pages to your project dependencies so your builds are consistent and reproducible....

The new and old image comes with quite a

The new and old image comes with quite a bit of tooling pre-installed, but neither of them install things at build time unless specified to do so. The old image does a confusing thing where it logs out stuff like "Attempting ruby version 2.7.1, read from environment" even if you didn't specify a ruby version in the environment. Those are effectively noops

pages.dev site reported as non-proxied

On the web analytics page The site in question is gnxi.srlinux.dev...

Pages Build Image v2 beta testers

Hey @Pages cloudflare , the Pages team is looking for beta testers for their new build system! (aka build image v2), they launched a build image update some weeks ago, but this new build system includes new versions by default and support for pnpm and Yarn 3, so if you'd like to test it, please drop your pages.dev url in the thread and feel free to leave your questions/feedback

hmm what specifically should I go turn

hmm, what specifically should I go turn off?

Both Note though that this only works

Both. Note though that this only works for Workers, not Pages

Using Pages CI You can open open the

Using Pages CI? You can open open the deployment logs and see if there's anything interesting there