and cloudflare worker is normal when set in wrangler.toml
and cloudflare worker is normal when set in wrangler.toml
IWrangler.toml does not apply to Pages.
Ayes, and i set that in dashboard, it not working
IThat's because nodejs_compat is different than node_compat.
nodejs_compat requires you to import from packages that start with
nodejs_compat requires you to import from packages that start with
node: whereas node_compat is a polyfill and allows you to use existing imports but with more limitations on what code you can import.Abut only nodejs_compat can be set in Compatibility flags, node_compat can only set in wrangler.toml with node_compat = true, is this right ?
Athat means pages not support node_compat ?
CPages doesn't support wrangler.toml except for local dev (which is confusing), and yes, no node_compat support (unless you manually bundle and deploy from wrangler), only nodejs_compat, Isaac explained the difference above.
If you need node_compat, you should probably just be using a Worker
If you need node_compat, you should probably just be using a Worker
Aok, thank you all. may be i can use worker as service binding for a workaround
Ai am using remix vite with cf and that only support pages, so maybe i will use service binding
FHello, i have a question.
So, my CF account get hijacked around a month ago. They changed the email linked to it. I didn't get notification when it happened. 20 days ago i already open ticket to CF service support. They said they will forward it to Trust & Safety Team. But, no news from them about it until now.
Is there any better way to fix this problem?
So, my CF account get hijacked around a month ago. They changed the email linked to it. I didn't get notification when it happened. 20 days ago i already open ticket to CF service support. They said they will forward it to Trust & Safety Team. But, no news from them about it until now.
Is there any better way to fix this problem?
KI'm trying to stop pages functions from being invoked for static assets on my next.js app and I'm struggling to get it to work. I've excluded all the routes for static assets in my _routes.json file and put the file in the public folder but still each page view will make 1-4 function requests. Any advice will be greatly appreciated!
HIIRC some of the files that Next.js generates are not in the static directory, so you usually end up with a few requests anyway
KI see. So it's possible that the functions are ignoring my static assets and the functions are just being invoked by random next.js stuff?
HMaybe? Check the network tab to see what your site requests when loading
Kthere is a lot of next.js stuff but it seems to mostly be in
/_next/static which I think is ignored by default. the rest of it is either my own static assets that are ignored in my _routes.json file or external assetsKis there some way to see the logs of the pages functions themselves? so I can see exactly what's invoking it?
KHere's my routes.json file:
K{"version":1,"description":"Built with @cloudflare/next-on-pages@1.9.0.","include":["/*"],"exclude":["/_next/static/*", "/public/*", "/favicon.ico", "/fonts/*", "/images/*"]}HYou can see in https://dash.cloudflare.com/?to=/:account/pages/view/:pages-project/:pages-deployment/functions, then scroll down to
Real Time Logs.Kfascinating, just went to that page and the invocation routes looks nothing like my
_routes.json
Kam I supposed to put _routes.json in a functions folder?
Kand yeah looking at the logs its triggering requests for
favicon.ico, fonts/*, etcHNo, it should be in the output directory. Do you see it in
.next/output, or whatever the output directory is?Kah yes I see one in
.vercel/output/staticnpx @cloudflare/next-on-pages. and it matches what's in the screenshot despite what I put into the custom _routes.jsonpublicdo you know how I'm supposed to properly add exclude routes? seems like it just defaults to this layout
HOh, actually remembering now. IIRC they intentionally don't provide custom
_routes.jsonYou might be able to fix it by manually replacing the file before upload
Ki see i see... but I'm not even tracking
.vercel on my repo. how can I modify the file on cloudflare servers?Kthank you so much for the help by the way
HHave
mv -f _routes.json .vercel/output/static/_routes.json in your build command?HOr something similar
Kah that's genius
Kim gonna give that a shot now
Kwoohoo!!!!
Kur a genius, thanks so much for the help
AQuick question:
During Direct upload using Wrangler, does wrangler push only the files with changes? Or all the files irrespective of it being changed or not?
During Direct upload using Wrangler, does wrangler push only the files with changes? Or all the files irrespective of it being changed or not?
HOnly the changed files
SHi team. I've opened a request (multiple times) to increase the soft limit for number of pages projects, but haven't heard back yet. Any chance you could take a look please?
CIf I upgrade to a paid plan, can I limit my budget for my apps?
CSo many ddos scandal recently 
HNot at the moment, though you can set a billing alarm
MAny chances that there is an issue right now where pages won't deploy based on my github pushes? Worked 3h ago abut not anymore
MSame issue here
MAh
HJust to check, is that documented somewhere? Did a quick check for _routes.json on the repo README and the linked docs, but couldn’t find anything…
JGitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
Kah yup this worked, thanks! seems like the issue was putting it in the
publicNot sure what that commenter is referring to. It was always in the root back to when I first implemented it a while ago
