XI just read on it and I guess its some sort of middleware to provide compatibility? How do I implement it?
IExactly, yeah. But generally you don't implement it yourself, there are packages to do it for you.
II'm not certain which ones would apply in this use-case however.
AThey’re like fake packages that copy the same style as the node ones so things work on browsers/workers
XAh I see
Xdoes postgres.js work out of the box on pages?
XI could try all of the alternative libraries, and if none work then look into some sort of polyfill solution
AThe Cloudflare Blog
Neon.tech is a database platform that allows you to branch your (Postgres compatible) database exactly like your code repository.And with the release of their Cloudflare Workers integration you can get started in minutes.
ATry this
XI'll definetally look into this. Also I've tried the documented "postgres + drizzle + workers" implementation but this was what started the issues in the first place
Xseems like the
pg
W
XThank you for pointing this out, I'm implementing this right now
XI'm running into an issue where trying to use AWS SES within pages does not work. A runtime error occurs:
Error: Dynamic require of \"node:buffer\" is not supportedIs there any way around this? I dont want to use other services like mailgun because they're way too pricey 
JThis is what I am currently doing to connect to a postgres db from within pages using the pg driver
1) Create a pages application, for mine I am using Remix.
2) Setup a worker called
3) Setup drizzle with an http proxy in your pages application. The pages app can use a service binding to call the
4) Make requests with drizzle, they will be proxied to your pages worker and your pages worker will use the connection pool from Hyperdrive.
With this setup you can connect to any postgres db.
For email using Amazon SES I was able to get @aws-sdk/client-ses working within a pages handler.
1) Create a pages application, for mine I am using Remix.
2) Setup a worker called
pg-proxy3) Setup drizzle with an http proxy in your pages application. The pages app can use a service binding to call the
pg-proxy4) Make requests with drizzle, they will be proxied to your pages worker and your pages worker will use the connection pool from Hyperdrive.
With this setup you can connect to any postgres db.
For email using Amazon SES I was able to get @aws-sdk/client-ses working within a pages handler.
AHi, I am using Cloudflare Turnstile captcha for my website. sometimes the captcha works but sometimes even if with the genuine user the captcha fails and returns error, not allowing user to do the payment. Please guide me on how to fix this ?
Nhow do I set node_compat for my page in dashboard?
N
NI am not sure it's this
HPages doesn't support
node_compatnodejs_compathow do i set
nodejs_compat
Nactually i have it set
Nit seems
IHi Cloudflare, do you have policies on .dev pages where phishing sites are swarming?
FIf you feel that a site is engaging in illegal or inappropriate activities, you can submit an abuse report at https://abuse.cloudflare.com/. The Trust and Safety team will review the details and reply if appropriate. You can also report the site to your relevant local authorities. Reports cannot be filed via Discord or with individual employees or Champs.
IThese are the phishing pages, I wonder what is your turnaround time for these? We already used your CloudFlare abuse forms, and it seems there are no actions
HWe can't do anything here. All Abuse-related actions can only be handled via the abuse form.
Ithanks 
IAnd when that won't work, who can we talk to? how do I even know if they are looking at my reports?
HThey are the only ones that can handle those reports
HThere isn't anything else we can do from here
SIs it possible to move the git repo ownership without impacting the page app setup?
XThank you for suggesting 
@aws-sdk/client-sesaws-sdk
AHello, does Cloudflare Pages support SSR sites? is using a lite node? or full node compatibility? I saw some posts that users complain that some packages don't work because the less node compatibility.
ICloudflare Pages supports SSR, but it's not Node - it's the Cloudflare Workers runtime, which is a lightweight JavaScript runtime that supports a smaller subset of Node features.
IQuite a few things work, especially with Node.js compatibility mode enabled, but some don't (e.g. there's no filesystem so no
fsThe only way to know for sure is to try it out with your specific use-case.
Athank you @Isaac McFadyen
JYeah been this way for a while. Definitely use the v3 libs
MWhy not point the domain there directly? What should the custom domain be used for if it doesn't point there?
DI was using git integration, for some reason I needed to use GitHub actions to build my pages project and deploy it using pages action. So I deleted the project and re-created it so I can use assets upload. But when I try to add my custom domain it says:
CDo you have any unpaid/partially paid invoices? iirc the billing migration has been messing with that a bit as well.
Otherwise you'll need to email that abusereply@ address
Otherwise you'll need to email that abusereply@ address
DNo, I sent an email.
Thank you.
Thank you.
DI didn't get the reply yet, if I don't know the problem how can I fix it. And what if the site was production ready, I may have lost many traffic?
