Im also here with a broken next-on-pages + Drizzle D1 App. Are there any docs on setupDevPlatform? N
Im also here with a broken next-on-pages + Drizzle D1 App. Are there any docs on setupDevPlatform? Not sure how to upgrade my app
LAre there any docs for next-on-pages + durable objects? 
BGitHub
If I understand correctly, version 1.9.0 removes the possibility to access your process.env.DB dev binding outside of a Route Handler. When using the v5/beta version of next-auth / auth.js, you nee...
DHi @wesbos 
These are the docs for the next-dev submodule and show you how to use
Please have a look and let me know if it's all clear
(PS: if you were using
(regarding Drizzle yeah we've gotta wait till next week to see if that's all fixed on the runtime I'm afraid)
(regarding Drizzle it should hopefully be all good now
)
These are the docs for the next-dev submodule and show you how to use
setupDevPlatformPlease have a look and let me know if it's all clear
(PS: if you were using
setupDevBindingswrangler.toml(regarding Drizzle it should hopefully be all good now
)GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
D@wesbos could you tell me if/how you've looked for the
I would love it if it would be easily discoverable and I hoped that this would do the trick:
https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflare-platform-integration
but if you had issues finding it maybe we've got a discoverability issue here? what do you think?
setupDevPlatformI would love it if it would be easily discoverable and I hoped that this would do the trick:
https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflare-platform-integration
but if you had issues finding it maybe we've got a discoverability issue here? what do you think?
GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
Dthis is what we've got 
: https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev#next-on-pages-next-dev
it briefly mentions DOs but that's acutally not too too helpful I'm afraid.... I'll add a note here: https://developers.cloudflare.com/workers/wrangler/api/#getplatformproxy
to better explain how to access DOs using
Anyways to use DOs you need to define them in your wrangler.toml file in this way:
and then before you run your next-on-pages app, in a separate terminal you need to spin up your "do-worker" worker
(you can't define a DO in your next-on-pages app but use the DO from a different worker)
I hope this helps, please let me know if it does
: https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev#next-on-pages-next-devit briefly mentions DOs but that's acutally not too too helpful I'm afraid.... I'll add a note here: https://developers.cloudflare.com/workers/wrangler/api/#getplatformproxy
to better explain how to access DOs using
getPlatformProxyAnyways to use DOs you need to define them in your wrangler.toml file in this way:
and then before you run your next-on-pages app, in a separate terminal you need to spin up your "do-worker" worker
(you can't define a DO in your next-on-pages app but use the DO from a different worker)
I hope this helps, please let me know if it does
WOh thanks! Apologies for not seeing that. My process was to google next-on-pages, which lead me to the github repo, I read that whole thing and then clicked each of the “references” links, then googled the method, didn’t see anything and then came here. I didn’t realize next-dev was a different module, would be great if there was a link in the main readme.
Dthere is!
D
WJust seeing now ugh
WYou can see the packages contents (with their documentation)
WSorry I just scrolled to the bottom and clicked the docs links. That might by be a user issue and not a docs issue haha
DI see
well it's valuable feedback in any case! thanks a bunch!
well it's valuable feedback in any case! thanks a bunch!
Dprobably having the next-dev module as a separate "internal package" helps making this a bit more confusing.... I would look into bring it into the next-on-pages package and remove this extra separation
WYeah, at least some docs on getting started without npx, I think a lot of people come at it from already having a next site and now want to figure out how to get it ready and bind services locally
D(I have an idea on how to do that, I'll need to experiment a bit with it.... the main problem being that the next-on-pages code outputs esm, but the next-dev code needs to output cjs since it gets required by the next dev server)
WI don’t envy that, I tried to convert a next project to ESM and I cried
Da migration doc right?
WYeah! I’m my case I was just looking for how to migrate to this new method, but since it’s such a mininal@setup it would be the same as an existing next project
DI'll think about it, thanks a bunch again for the valuable feedback
WAnytime!
MHey there! recently Prisma released a preview for connecting to PlanetScale via CF/Next-on-pages however I can't seem to get it to work, and was wondering if there was example code anywhere?
JI'm not sure what exactly you're referring to? Is there anything you can share about it?
Muno momento
MPrisma on Notion
These are Cloudflare-specific instructions for @Prisma + Edge Functions Early Access
Mthe bottom of that
MI mean I'm running into a million and one issues other than Prisma/Planetscale like,
but this seems to be a webpack issue (?)
but this seems to be a webpack issue (?)
JYeah I have absolutely no idea where that would come from, but it's probable that's something to do with how Next.js uses webpack(?)
JAh an early access thing, yeah, if anyone has an example it'll be the prisma team! Afraid that's not very helpful...
Mno problemo haha cheers for the help!
Myeah it's really irritating me as I'm pretty much stuck, I believe it's the fact I'm using clerk on the edge too but that seems to be compatible
JI recall clerk had issues early on with the edge but they worked with the vercel team to resolve those so i would be surprised if they were still problematic
Mmmm, gonna see if just hosting it on vercel somehow makes it work
Mscratch that, I can't get it to build locally now 
J
MI'm managing to get npm run build & turbo build working but I'm running into this issue again with the next-on-pages command pages-helpno such file or directory
Dsame here, wasm imports don't work with next-on-pages
https://github.com/cloudflare/next-on-pages/issues/676
https://github.com/cloudflare/next-on-pages/issues/676
GitHub
next-on-pages environment related information System: Platform: linux Arch: x64 Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023 CPU: (12) x64 AMD Ryzen 5 5500U with Radeon Graphics Memory: 3 GB Shell: ...
MAnyone know when this stuff could be fixed by? As it’s a blocker for me to launch on CF and the only other alternative is Vercel - which I don’t really want to use
Mlooks like a bunch of other people are also running into this issue btw, I'll list relevant GH issues/comments in pages-helpno such file or directory
WHey folks - trying to migrate from the previous
setupDevBindingssetupDevPlatform- I've got it working except it seems to not be pointing at the correct local sqlite DB for the D1 driver.
JHi @mr nooli @Deo Kumar, I've opened a PR that should fix this - please can you try this prerelease.
Vdoes nextjs app router and pages router apps run fine on pages? are there any limitations apart from image optimisations?
MYep absolutely does! I was for a short time running https://cruncho.app on there but the app got too big that pages stopped being able to build it :/ which meant I had to unfortunately switch back to Vercel
FHeyo!
I am suddenly getting "build exceeded memory limit", but the only thing I did was change from client pages using route handlers to server-sided api calls, is there something going on? I am unsure why this is suddenly happening :/
I am suddenly getting "build exceeded memory limit", but the only thing I did was change from client pages using route handlers to server-sided api calls, is there something going on? I am unsure why this is suddenly happening :/
Frunning npm run build locally works fine, but on cloudflare pages it takes about 5 minutes at least and then it just stops
MI had this issue too a while back with Cruncho, didn't dig into it too much, just figured that there wasn't another option than to switch away, but hopefully someone will be able to help you out!
MAn 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?
