Yeah, at least some docs on getting started without npx, I think a lot of people come at it from alr

D

Dario•2/25/24, 2:03 PM

(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)

W

wesbosOP•2/25/24, 2:04 PM

I don’t envy that, I tried to convert a next project to ESM and I cried

Wwesbos Yeah, at least some docs on getting started without npx, I think a lot of people...

D

Dario•2/25/24, 2:04 PM

a migration doc right?

W

wesbosOP•2/25/24, 2:05 PM

Yeah! 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

D

Dario•2/25/24, 2:06 PM

I'll think about it, thanks a bunch again for the valuable feedback

W

wesbosOP•2/25/24, 2:08 PM

Anytime!

M

mr nooli•2/25/24, 2:46 PM

Hey 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?

J

James•2/25/24, 2:58 PM

I'm not sure what exactly you're referring to? Is there anything you can share about it?

M

mr nooli•2/25/24, 3:08 PM

uno momento

M

mr nooli•2/25/24, 3:08 PM

https://prismaio.notion.site/Prisma-Cloudflare-Workers-and-Pages-107091db465f4ae08606dbf3070a0821#c72ffa35c1124449abeb4a6f2194ad48

Prisma on Notion

Prisma + Cloudflare Workers and Pages | Notion

These are Cloudflare-specific instructions for @Prisma + Edge Functions Early Access

M

mr nooli•2/25/24, 3:08 PM

the bottom of that

M

mr nooli•2/25/24, 3:13 PM

I mean I'm running into a million and one issues other than Prisma/Planetscale like,

[Error: ENOTDIR: not a directory, open '/Volumes/Primary/Code/cms/.next/server/edge-chunks/wasm_8b5add1f3c1bcd5e8c85235d4465ef1ec3674e24.wasm'] {
build:   errno: -20,
build:   code: 'ENOTDIR',
build:   syscall: 'open',
build:   path: '/Volumes/Primary/Code/cms/.next/server/edge-chunks/wasm_8b5add1f3c1bcd5e8c85235d4465ef1ec3674e24.wasm'
build: }

[Error: ENOTDIR: not a directory, open '/Volumes/Primary/Code/cms/.next/server/edge-chunks/wasm_8b5add1f3c1bcd5e8c85235d4465ef1ec3674e24.wasm'] {
build:   errno: -20,
build:   code: 'ENOTDIR',
build:   syscall: 'open',
build:   path: '/Volumes/Primary/Code/cms/.next/server/edge-chunks/wasm_8b5add1f3c1bcd5e8c85235d4465ef1ec3674e24.wasm'
build: }

[Error: ENOTDIR: not a directory, open '/Volumes/Primary/Code/cms/.next/server/edge-chunks/wasm_8b5add1f3c1bcd5e8c85235d4465ef1ec3674e24.wasm'] {
build:   errno: -20,
build:   code: 'ENOTDIR',
build:   syscall: 'open',
build:   path: '/Volumes/Primary/Code/cms/.next/server/edge-chunks/wasm_8b5add1f3c1bcd5e8c85235d4465ef1ec3674e24.wasm'
build: }

[Error: ENOTDIR: not a directory, open '/Volumes/Primary/Code/cms/.next/server/edge-chunks/wasm_8b5add1f3c1bcd5e8c85235d4465ef1ec3674e24.wasm'] {
build:   errno: -20,
build:   code: 'ENOTDIR',
build:   syscall: 'open',
build:   path: '/Volumes/Primary/Code/cms/.next/server/edge-chunks/wasm_8b5add1f3c1bcd5e8c85235d4465ef1ec3674e24.wasm'
build: }

but this seems to be a webpack issue (?)

J

James•2/25/24, 3:21 PM

Yeah 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(?)

Mmr nooli https://prismaio.notion.site/Prisma-Cloudflare-Workers-and-Pages-107091db465f4ae...

J

James•2/25/24, 3:22 PM

Ah an early access thing, yeah, if anyone has an example it'll be the prisma team! Afraid that's not very helpful...

M

mr nooli•2/25/24, 4:07 PM

no problemo haha cheers for the help!

JJames Yeah I have absolutely no idea where that would come from, but it's probable tha...

M

mr nooli•2/25/24, 4:08 PM

yeah 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

J

James•2/25/24, 4:12 PM

I 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

M

mr nooli•2/25/24, 4:25 PM

mmm, gonna see if just hosting it on vercel somehow makes it work

M

mr nooli•2/25/24, 4:27 PM

scratch that, I can't get it to build locally now

J

James•2/25/24, 4:31 PM

M

mr nooli•2/25/24, 4:33 PM

I'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

Mmr nooli I'm managing to get npm run build & turbo build working but I'm running into thi...

D

Deo Kumar•2/26/24, 8:23 AM

same here, wasm imports don't work with next-on-pages
https://github.com/cloudflare/next-on-pages/issues/676

GitHub

[🐛 Bug]: wasm imports don't work · Issue #676 · cloudflare/next-on-...

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: ...

M

mr nooli•2/26/24, 10:16 AM

Anyone 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

M

mr nooli•2/26/24, 4:41 PM

looks 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

W

wesbosOP•2/26/24, 6:33 PM

Hey folks - trying to migrate from the previous

setupDevBindings

setupDevBindings

setupDevBindings

setupDevBindings to the new

setupDevPlatform

setupDevPlatform

I've got it working except it seems to not be pointing at the correct local sqlite DB for the D1 driver.

his was my previous config file, have I not specified the wrangler toml correctly?

setupDevBindings({
        bindings: {
          D1: {
            type: "d1",
            databaseName: "podcast-stats-prod",
            id: "e2659b9a-928c-4218-beb5-518b87f59c4f",
          },
        },
      });

setupDevBindings({
        bindings: {
          D1: {
            type: "d1",
            databaseName: "podcast-stats-prod",
            id: "e2659b9a-928c-4218-beb5-518b87f59c4f",
          },
        },
      });

setupDevBindings({
        bindings: {
          D1: {
            type: "d1",
            databaseName: "podcast-stats-prod",
            id: "e2659b9a-928c-4218-beb5-518b87f59c4f",
          },
        },
      });

setupDevBindings({
        bindings: {
          D1: {
            type: "d1",
            databaseName: "podcast-stats-prod",
            id: "e2659b9a-928c-4218-beb5-518b87f59c4f",
          },
        },
      });

[[d1_databases]]
binding = "D1"
database_name = "podcast-stats-prod"
database_id = "e2659b9a-928c-4218-beb5-518b87f59c4f"

[[d1_databases]]
binding = "D1"
database_name = "podcast-stats-prod"
database_id = "e2659b9a-928c-4218-beb5-518b87f59c4f"

[[d1_databases]]
binding = "D1"
database_name = "podcast-stats-prod"
database_id = "e2659b9a-928c-4218-beb5-518b87f59c4f"

[[d1_databases]]
binding = "D1"
database_name = "podcast-stats-prod"
database_id = "e2659b9a-928c-4218-beb5-518b87f59c4f"

Mmr nooli Anyone know when this stuff could be fixed by? As it’s a blocker for me to launc...

J

James•2/26/24, 8:34 PM

Hi @mr nooli @Deo Kumar, I've opened a PR that should fix this - please can you try this prerelease.

V

vish•2/27/24, 4:55 AM

does nextjs app router and pages router apps run fine on pages? are there any limitations apart from image optimisations?

Vvish does nextjs app router and pages router apps run fine on pages? are there any li...

M

mr nooli•2/27/24, 8:53 AM

Yep 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

Cruncho - Restaurant Management Software

F

faye•2/27/24, 12:12 PM

Heyo!

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 :/

F

faye•2/27/24, 1:05 PM

running npm run build locally works fine, but on cloudflare pages it takes about 5 minutes at least and then it just stops

Ffaye Heyo! I am suddenly getting "build exceeded memory limit", but the only thing I...

M

mr nooli•2/27/24, 1:18 PM

I 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!

M

mr nooli•2/27/24, 1:18 PM

An alternative - use GH to build your app and then push it to CF workers using wrangler, but it's a less elegant solution.

Mmr nooli An alternative - use GH to build your app and then push it to CF workers using w...

F

faye•2/27/24, 4:04 PM

The 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 :/

F

faye•2/27/24, 4:04 PM

W

wesbosOP•2/28/24, 6:46 PM

hey 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?

B

Befus•2/28/24, 9:31 PM

I deleted my KV bindings since I switched to D1 but my builds are failing because somehow the builds still think they are there?

B

Befus•2/28/24, 9:32 PM

B

Befus•2/28/24, 9:33 PM

My build cache is cleared and disabled now

W

wesbosOP•2/29/24, 3:50 PM

Anyone 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?

W

wesbosOP•2/29/24, 3:51 PM

Actually if I can add a scheduled handler to my worker, I could just re-implement the vercel.json cron with a switch case

W

wesbosOP•2/29/24, 7:55 PM

Just 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

James•3/1/24, 1:37 PM

F

faye•3/1/24, 11:10 PM

Hey,

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:

F

faye•3/1/24, 11:10 PM

This is the log from the deployment

headpat-de.dc4227ab-2cac-4127-937a-cb9e9be828c3.log28.19KB

F

faye•3/1/24, 11:13 PM

Only the pre-rendered routes work (however they only work partly and are extremely broken..)

F

faye•3/1/24, 11:16 PM

I 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 :/

L

luna•3/2/24, 2:25 AM

im trying to use ai with next on pages and im not sure where im going wrong.

Screenshot_2024-03-02_at_12.53.46_pm.png

K

kian•3/2/24, 2:43 AM

K

kian•3/2/24, 2:43 AM

CompressionStream isn't even a Node API, is it? It's a Web API which has been supported by browsers (and Workers) for years.

K

kian•3/2/24, 2:43 AM

That's a weird error.

Yeah, at least some docs on getting started without npx, I think a lot of people come at it from alr

Similar Threads