An alternative - use GH to build your app and then push it to CF workers using wrangler, but it's a
An alternative - use GH to build your app and then push it to CF workers using wrangler, but it's a less elegant solution.
FThe issue with using wrangler, it's for static content
As I am using non-static content as well, it's not for me. But as said it worked fine for me but suddenly it's taking like 6 minutes just to build (instead of 3 for example, and after 5:45-6 minutes, it just says this, super disappointing and would love to know why this is happening :/
As I am using non-static content as well, it's not for me. But as said it worked fine for me but suddenly it's taking like 6 minutes just to build (instead of 3 for example, and after 5:45-6 minutes, it just says this, super disappointing and would love to know why this is happening :/
F
Whey folks- having trouble deploying my app to cloudflare. It seems only the static bits are being uploaded, I dont see any of the dynamic routes being turned into functions, or any of the bindings I've setup in settings show up. Should I be?
BI deleted my KV bindings since I switched to D1 but my builds are failing because somehow the builds still think they are there?
B
BMy build cache is cleared and disabled now
WAnyone have approaches for cron jobs with next-on-pages? I'd assume you can't use Cloudflare scheduled triggers within the same worker. Maybe another worker that pings our API endpoints?
WActually if I can add a scheduled handler to my worker, I could just re-implement the vercel.json cron with a switch case
WJust wanted to say thanks + fantastic job on the next-on-pages adaptor. I'm very impressed that all the cache + revalidate stuff "just works", and the development experience was really smooth.
J
FHey,
I published a version of nextjs on a cloudflare page using git integration, but it's failing miserably.
I would like some help ASAP if possible, the page build succeeds, but nothing of the page itself makes sense.
Routes are missing, the front page (static) shows a 404, the real-time logs show this:
I published a version of nextjs on a cloudflare page using git integration, but it's failing miserably.
I would like some help ASAP if possible, the page build succeeds, but nothing of the page itself makes sense.
Routes are missing, the front page (static) shows a 404, the real-time logs show this:
FThis is the log from the deployment
FOnly the pre-rendered routes work (however they only work partly and are extremely broken..)
FI don't know what to do about it :(
If something is wrong on my end, CF is giving me none of it, it's just ending the entire page sadly :/
If something is wrong on my end, CF is giving me none of it, it's just ending the entire page sadly :/
Lim trying to use ai with next on pages and im not sure where im going wrong. 
K
KCompressionStream isn't even a Node API, is it? It's a Web API which has been supported by browsers (and Workers) for years.
KThat's a weird error.
UDoes cloudflare ai really use the vercel ai package? 
UOr is this vercel being dumb and in the build of nextjs not allowing an api to be used at all
UI see
K
UGitHub
What's in there?
Middleware, since they are ran on edge runtime, do not have access to Node.js globals. While #36434 addressed cases where a middleware would import a node.js module, this PR is...
Middleware, since they are ran on edge runtime, do not have access to Node.js globals. While #36434 addressed cases where a middleware would import a node.js module, this PR is...
Ulol trying to file an issue on the nextjs repo is way too much effort
Lso that warning just needs to be disabled for next-on-pages, correct?
UI dont think next-on-pages can modify that at all needs to be fixed on the actual nextjs repo
Lno no i get that. what im asking is, this is supported when deployed correct? (if we get the error removed will it work?)
UOh I see, yes it would work when that is removed.
Lin that case i wonder if i can get around this for now with patch-package. 
FCould someone help me with this? Would be super greatful :x
FRunning npm run build & npm run start works fine locally for me too
JCan you try redeploying?
FI did a lot of times, I changed a lot of the code, nothing helps
FThey all succeed the build too, the real-time logs doesn't work (i get that error i previously posted, the image with the account not being found), i even created a new repo and made a new CF Page, still did not work
FEven worse: Using 
npx wrangler pages dev -- npm run start also works.. FUpdate:
After making a new git repo and moving files one after one.. I figured something out.
Adding literally any page other than the main page shows a "Worker threw exception".. Literally anything, even a simple page using this:
I'm so annoyed about this, why is CF having so many issues with this project?
After making a new git repo and moving files one after one.. I figured something out.
Adding literally any page other than the main page shows a "Worker threw exception".. Literally anything, even a simple page using this:
I'm so annoyed about this, why is CF having so many issues with this project?
FFremoving the forgot-password folder will make it work again, is anyone able to help with this? I really need to continue :/
FFrom the real-time logs (that actually work now):
Uhttps://2f0267bb.headpat-web.pages.dev/(main) this kinda works it does a 404 instead lolFwhich makes no sense, it's a normal page: https://github.com/Headpat-Community/web/blob/main/src/app/(main)/page.jsx
Flol
FSo I'm guessing this is a cloudflare issue and not on my side? Wouldn't for the life of me know where to look with literally no pages 
UI'd probably remove
(main) as the folder name and just make it main and see if it works. Might be because of the non url safe charactersJit's a route group - a next.js feature for grouping routes with layouts in the app directory
Jbut yes, this is likely a cloudflare issue
Fthis, i also have other pages using the same exact things, there's close to no difference which the structure of the website
FWhat do I do?
