you can't use pages functions if you're using next-on-pages - you need to use nextjs API routes inst
you can't use pages functions if you're using next-on-pages - you need to use nextjs API routes instead
IHaha - be nice if that was mentioned somewhere prominent. Where might I find some guidance on integrating D1 using api routes? Am I still required to use bindings etc etc?
IOk, turns out that was very easy - thank you for the information James.
JNo worries
BSearching through the chat logs here I saw your message. Wanted to share some more on this.
I also have this same issue, and shared it on the Nextjs discord and apparently others also have this on just Cloudflare:
https://discord.com/channels/752553802359505017/1267103626967650375
Normally I would create a Github Issue but honestly I have no clue what the reproduction steps are. It happens with the bare minimum already.
I also have this same issue, and shared it on the Nextjs discord and apparently others also have this on just Cloudflare:
https://discord.com/channels/752553802359505017/1267103626967650375
Normally I would create a Github Issue but honestly I have no clue what the reproduction steps are. It happens with the bare minimum already.
BI'm unable to find any additional information in the logs on CF Pages either
Byeah its a weird bug, specific to cloudflare, but unless you forcefully refresh your website, it doesnt occur on it's own
VHow would i debug this? only hapens on deployment and not when building localy
Vhavent updated anything, it just happened on a random commit that changed some text
Vretrying deployment 2 times somehow fixed it...
SHow can I still use my nginx proxy with this?
SMy frontend should be port 8080, backend port 3000
using paths, not subdomains
using paths, not subdomains
JHi everyone, I'm getting an error when deploying after creating a new Next.js project using C3:npm run preview
...
Completed
✘ [ERROR] Could not resolve "pcre-to-regexp/dist/index.js"
node_modules/@cloudflare/next-on-pages/templates/_worker.js/utils/pcre.ts:5:23:
5 │ import createPCRE from 'pcre-to-regexp/dist/index.js';
╵~~~~~~
The Yarn Plug'n'Play manifest forbids importing "pcre-to-regexp" here because it's not listed as a
dependency of this package:
../../../.pnp.cjs:36:31:
36 │ "packageDependencies": [\
╵
You can mark the path "pcre-to-regexp/dist/index.js" as external to exclude it from the bundle,
which will remove this error.
✘ [ERROR] Could not resolve "cookie"
node_modules/@cloudflare/next-on-pages/templates/_worker.js/routes-matcher.ts:1:22:
1 │ import { parse } from 'cookie';
╵~~
The Yarn Plug'n'Play manifest forbids importing "cookie" here because it's not listed as a
dependency of this package:
../../../.pnp.cjs:36:31:
36 │ "packageDependencies": [\
╵ ~~
You can mark the path "cookie" as external to exclude it from the bundle, which will remove this
error.
Unexpected error: Build failed with 2 errors:
node_modules/@cloudflare/next-on-pages/templates/_worker.js/routes-matcher.ts:1:22: ERROR: Could not resolve "cookie"
node_modules/@cloudflare/next-on-pages/templates/_worker.js/utils/pcre.ts:5:23: ERROR: Could not resolve "pcre-to-regexp/dist/index.js"
next-cf-demo@0.1.0 preview
npm run pages:build && wrangler pages dev
next-cf-demo@0.1.0 pages:build
npx @cloudflare/next-on-pages
...
Completed npx vercel build✘ [ERROR] Could not resolve "pcre-to-regexp/dist/index.js"
node_modules/@cloudflare/next-on-pages/templates/_worker.js/utils/pcre.ts:5:23:
5 │ import createPCRE from 'pcre-to-regexp/dist/index.js';
╵
The Yarn Plug'n'Play manifest forbids importing "pcre-to-regexp" here because it's not listed as a
dependency of this package:
../../../.pnp.cjs:36:31:
36 │ "packageDependencies": [\
╵
You can mark the path "pcre-to-regexp/dist/index.js" as external to exclude it from the bundle,
which will remove this error.
✘ [ERROR] Could not resolve "cookie"
node_modules/@cloudflare/next-on-pages/templates/_worker.js/routes-matcher.ts:1:22:
1 │ import { parse } from 'cookie';
╵
The Yarn Plug'n'Play manifest forbids importing "cookie" here because it's not listed as a
dependency of this package:
../../../.pnp.cjs:36:31:
36 │ "packageDependencies": [\
╵ ~~
You can mark the path "cookie" as external to exclude it from the bundle, which will remove this
error.
Unexpected error: Build failed with 2 errors: node_modules/@cloudflare/next-on-pages/templates/_worker.js/routes-matcher.ts:1:22: ERROR: Could not resolve "cookie" node_modules/@cloudflare/next-on-pages/templates/_worker.js/utils/pcre.ts:5:23: ERROR: Could not resolve "pcre-to-regexp/dist/index.js"
THey, do you have any public repo with this implementation? I have been trying but has not been very successful. Thanks
KNah not really sorry, it should still be the same still from memory just using , getting any error?
KI think the only issue i've had with it, is trying to use --turbo when running npm run dev which doesn't work with the auth js beta-19
TAhh gotcha. I think I am messing by while connecting to the d1 db. Let me try a bit more tho
HHello there
I'm having issue connecting my github account to my cloudflare pages for deployment, i keep getting
an error occurred, i should contact
I'm having issue connecting my github account to my cloudflare pages for deployment, i keep getting
an error occurred, i should contact
Hhello there
JAnyone else working with next-on-pages and having issues with the
__NEXT_ON_PAGES__KV_SUSPENSE_CACHE, for us the KV is never being populated with fetch data, even when I use force-cache
Eyou can't, it's not supported
JHello everyone
Has anyone ever experienced an error where the data shows fine on local host but deployed get status 200 but the data is nowhere to be found
https://github.com/Jorgo55/newpages-for-freelancers
here is a more detailed description of the issue if you want to check it out
i am ready to reward anyone if they can help me
thanks for more info just hmu here on discord
Has anyone ever experienced an error where the data shows fine on local host but deployed get status 200 but the data is nowhere to be found
https://github.com/Jorgo55/newpages-for-freelancers
here is a more detailed description of the issue if you want to check it out
i am ready to reward anyone if they can help me
thanks for more info just hmu here on discord
GitHub
New Pages for freelancers to check out cloudflare and Next js problem on displaying data - Jorgo55/newpages-for-freelancers
JI don't know why there is a .pnp.cjs file in my ~/ directory(maybe there are some mistakes in setting up yarn). It shouldn't be there. After deleting it, everything worked fine. Thank you for your help 
JI updated my issue @ https://github.com/cloudflare/next-on-pages/issues/844 seems to be related to the worker version, will also cross post to those channel(s)
GitHub
next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.5.0: Wed May 1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000 CPU...
Jfwiw I disagree with using KV for fetch cache generally and have since we first implemented it since it's eventually consistent which means managing the manifest for the cache is unreliable (and fetch cache is supposed to be regional according to Vercel docs)
JBut it's described as "So for the above reasons the Workers KV storage solution is the one we recommend." in the docs?
Jyep and I disagree with that statement in the docs and don't think it should be there
AHow can I disable the cache without
Or is there no cache on production? There is in local.
cache: 'no-store'?Or is there no cache on production? There is in local.
IYou can do
fetch(..., { next: { revalidate: 0 }})JIs there a way for my D1 binding migrations to be executed when I deploy my next-on-pages app? I know you can do it using the CLI but I wonder if it also works automatically?
SIs there any update on Gradual Deployments for Pages?
FHey guys!
I am suddenly having an issue with my pages project, would love some help asap.
The project worked perfectly fine before and still does locally. However suddenly it just gives random 403 Forbidden on api requests and internal server errors on other pages.
Example:
I am suddenly having an issue with my pages project, would love some help asap.
The project worked perfectly fine before and still does locally. However suddenly it just gives random 403 Forbidden on api requests and internal server errors on other pages.
Example:
https://d8bad4bc.cloudnet-webinterface.pages.dev/en/sasag (anything that doesn't exist should give a proper 404, but it doesn't in this deployment..?)
FRe-deploying doesn't help.
Sometimes it fixes the internal server error and the next deployment it will do the same thing again.
And the signing in doesn't work at all. No matter what I do to the /api/user/signin url, it shows me a 403, and only on cloudflare pages. So annoying
Sometimes it fixes the internal server error and the next deployment it will do the same thing again.
And the signing in doesn't work at all. No matter what I do to the /api/user/signin url, it shows me a 403, and only on cloudflare pages. So annoying
FIt even works using wrangler pages dev.. https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#build-and-preview-your-application-locally
Why not on cloudflare itself?
Why not on cloudflare itself?
FIf someone is able to help, please ping/reply so I get pinged.
WWhere's the API request to? Sounds like they may be blocking workers
FIt's to /api/user/signin, which has a POST in it going to a CloudNet instance (open source project), just making a normal basic btoa auth, cors is also on
*just an IP:2814
FHm.. thanks for the "tip", I just figured out that if you use a domain instead of IP, it does work. Took me days lol
FAlthough the internal server error has nothing to do with this issue AFAIK, as it's just a "not found" route
CWorkers can't fetch IPs and have restrictions on fetching specific ports
C(flowchart by community mvp albert)
MWhen using Nextjs, would you advise using Cloudflare Functions or nextjs-on-pages and Nextjs API route?
So what are the pros and cons besides Functions is Cloudflare exklusive?
So what are the pros and cons besides Functions is Cloudflare exklusive?
Jnextjs API routes if you want to use SSR. if you want your site to just be SSG, you don't need next-on-pages
MMy nextjs app is taking a long time to compile even sir small change is there any way to speed it up or it's my laptop problem
IDev mode or to compile for production?
