MWith Baselime, is there any integration with next on pages? In their docs it seems like all it does for pages is capture logs and it has to be instantiated and "flushed" in each function to be able to do that. Since it got acquired by CF, I figured I should start learning it, but it seems pretty limited in functionality unless I'm majorly missing something. Anyone able to shed any light?
Jnot yet, something funky is happening in that pr that I'm going to look into this weekend
JSo bad luck and bad timing 
It looks like 1.11.3 actually did fix the issue we encountered. After redeployment with an updated package.json and the most recent NodeJS LTS version it works as expected. Thank you very much.
So rule of thumb: Whenever we encounter the 1101 error: Call for help here?
It looks like 1.11.3 actually did fix the issue we encountered. After redeployment with an updated package.json and the most recent NodeJS LTS version it works as expected. Thank you very much.So rule of thumb: Whenever we encounter the 1101 error: Call for help here?
JGitHub issue on the next-on-pages repo ideally, both Dario and I will see it. in this case thankfully the person who reported the issue also managed to figure out the cause, otherwise we probably wouldn't have been able to find it
MWhen trying to deploy it is forcing me to use edge runtime, even though i have made dynamic false
here is link to github issue which was reported by someone else
https://github.com/cloudflare/next-on-pages/issues/745
here is link to github issue which was reported by someone else
https://github.com/cloudflare/next-on-pages/issues/745
GitHub
next-on-pages environment related information Relevant Packages: @cloudflare/next-on-pages: 1.11.0 vercel: N/A next: 14.1.4 Description I'm currently building a website with Next.js 14 and Pris...
MI am also generating meta data just like this example
LUpdate: I think I've got the Next.js app in a satisfying state:
- Moved most server components and server action "magic" to good old client components with api routes HTTP calls from the user's browser.
- The data flow just makes more sense mentally, and it gives you a chance to test backend logic from outside the nextjs app (with postman for example).
- With Tanstack Query client side you can also retry queries if they go wrong or while waiting for a database update for example.
- Moved the critical and hard to debug Stripe payment logic to standalone (different project) workers. I now have 2 stripe webhooks workers waiting for POST calls from stripe, one in stripe test mode, one in stripe live mode. Having a deployed test mode worker that is bound to a deployed D1 database was key for my debugging. D1 was rejecting writes because of a foreign key constraint (I was passing the wrong id).
- Enabled logpush for the standalone workers (don't forget to add `logpush = true` in wrangler.toml after enabling logpush in the dashboard). Now my logs are persisted and I can go check what went wrong in prod for these critical workers.
- Next step, looking for a simple way to access / read / sort / filter the log.gz files that are on R2. Is there an app that makes it simple? Or are most people using command-line jq as specified here? https://developers.cloudflare.com/logs/tutorials/parsing-json-log-data/
3looking for advice on how to structure a "white-label" monorepo-ish website that has:
- base template/starter repo that includes ui components, middleware, auth etc (essentially everything except website content)
- child website/content repos are built with the above foundation and have their own configuration/content/components
- changes to base template should ripple and update for all child websites
my current issue is cf pages only allows you to use a github repo once (5 times if it is a monorepo) so i want to avoid doing some weird git submodule trickery. any advice how i should proceed?
Jno need to apologize, they were valid criticisms/frustrations
Lis it possible to use a service binding while developing locally(next dev) to a worker that is already deployed?
JAnything I can do to assist?delete our e2es
Jbasically it doesnt make any sense why they're failing for a middleware test
Joh crap
Ji found it and it's a big oopsie
Ji believe it should all be fixed now, dario will likely have a look tomorrow
J
MWhat features am I losing moving my next 14 web app from vercel to cloudflare
Jhttps://github.com/cloudflare/next-on-pages/blob/main/packages/next-on-pages/docs/supported.md is probably a good place to start for reference
RI've looked around the documentation and am struggling a bit, is there anything extra you need to do to render a Cloudflare function on a path besides create a file in the
but when I run
functions directory? I have a simple helloworld.ts that returns the documentation example but when I run
npm run dev/helloworld I don't see the hello world text. Jthe functions directory does not work with next-on-pages as we generate our own worker for your app. you should be using nextjs API routes
RThanks! That clears up some confusion for me.
RMe learning Cloudflare pages lol
Jwe're going to park it termporarily because i'm concerned it might interfere with how nextjs fetch caching works, since this is to fix an issue in the react fetch patch which is a layer deeper than the nextjs fetch patch i believe
Jif you want to use the changes in this pr, you can use the prerelease linked in it
Jhttps://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/9067847845/npm-package-next-on-pages-771Jyou can change it to
npx https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/9067847845/npm-package-next-on-pages-771 and it will build using the build for this prJsounds good
SDid disabling "smart placement" fix the internal server error for you? I ask as we're having the same issue but we don't have smart placement enabled at all. Wondering if it's something else? Our issue seems to be very random, almost like it's capacity related (too many hits in a short amount of time).
Nyes it did
NHello everyone,
I have a problem uploading my nextjs application in cloudflare using the build command for "normal nextjs" / not static nextjs. I have some dynamic paths / routes where I'm using some server built-in packages (e.g. crypto / http / etc...). Cloudflare requires me to put , while I need "use server" at the top of my page. When trying to build the application on Cloudflare, it gives an errors saying that needs to be async / all functions need to be async.
Is there any solutions to it?
I have a problem uploading my nextjs application in cloudflare using the build command for "normal nextjs" / not static nextjs. I have some dynamic paths / routes where I'm using some server built-in packages (e.g. crypto / http / etc...). Cloudflare requires me to put , while I need "use server" at the top of my page. When trying to build the application on Cloudflare, it gives an errors saying that needs to be async / all functions need to be async.
Is there any solutions to it?
Nyou need to put
export const runtime = "edge";"use server" is for server actions so I think you need to separate that into a different fileNexport const
do i have to put this in every page.tsx / route.ts / layout.tsx ?
do i have to put this in every page.tsx / route.ts / layout.tsx ?
Nevery page.tsx / route.ts that are not static (that use headers, cookies etc)
Nbut you don't need for your server action
LVercel image optimization, log drains for log retention, sentry integration