You cannot, unfortunately. You need to recreate the project manually
You cannot, unfortunately. You need to recreate the project manually
Iokay, I have already deleted and created the project again
SAll, lets say I setup a nextjs app on Pages (Full stack) and added a page function to the functions folder (similar to of nextjs API). Once my function finishes (not middle ware, but some real work being done like updates to some database), would i be able to forward to a page in nextjs? I am not really seeing many examples of context.next() that sends it back to another nextjs screen ? (I have seen examples of forwards(?) to static assets using env.ASSETS....). I also find context.next() used in terms of middleware, but cant find reference to how I get back to my UI App without doing a redirect. Effectively, I want response coming from UI App(nextjs), not from a Page function after it does its work.
NAnyone have any good examples of using wrangler to deploy to pages in a CI environment? Doesn't matter the CI provider, I'm just not finding what I need in the docs, and the CF runners don't have enough ram for our build process
KYou do your own build as usual, and use
wrangler pages deploy ./output where outputThere are flags you need to pass, like the project - the rest can be inherited from Git (branch, commit SHA, etc)
K
NThanks for the quick reply. I tried that originally, but just realized I specified the wrong directory path, seems to work now. Thanks again!
Pis there a way to set a preview build to a custom domain? e.g. that the staging branch is linked to staging.xyz.com?
NWe added a custom domain linked to a branch alias and it seems to work
KCloudflare Docs
In this guide, you will learn how to add a custom domain (staging.example.com) that will point to a specific branch (staging) on your Pages project.
Pah yeah - thanks - should have checked if i find something in the docs first...
KIt's not the most polished experience to get it setup but it does work fine once it's done.
Pis there a way to tell a nuxt pages the environment? tried it with NODE_ENV in the pages settings but it does not care.
Ahow cloudflare pages set node_compat, i set nodejs_compat flag in dashboard, but it does not work
Aand 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 file
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/static after running npx @cloudflare/next-on-pages. and it matches what's in the screenshot despite what I put into the custom _routes.json file in the public folder (it even overwrites the one in the public folder)Kdo 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.json support with NextOnPages because it breaks middlewareHYou 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
