I'm managing to get npm run build & turbo build working but I'm running into this issue again with t

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

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

mr nooliOP•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

mr nooliOP•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

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

Hey folks - trying to migrate from the previous setupDevBindingssetupDevBindings to the new setupDevPlatformsetupDevPlatform

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",
          },
        },
      });

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

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.

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

mr nooliOP•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

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

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

mr nooliOP•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!

mr nooliOP•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...

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

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

wesbos•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?

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?

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

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

My build cache is cleared and disabled now

wesbos•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?

wesbos•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

wesbos•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.

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

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:

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

This is the log from the deployment

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

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

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

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

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

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

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.

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

That's a weird error.

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

https://github.com/vercel/next.js/blob/04b13f52a5e2d3d28515a01996a8c92ce823bb30/test/integration/edge-runtime-with-node.js-apis/test/index.test.ts#L33

Unsmart•3/2/24, 2:51 AM

Does cloudflare ai really use the vercel ai package? Hmmge

Unsmart•3/2/24, 2:55 AM

Or is this vercel being dumb and in the build of nextjs not allowing an api to be used at all

UUnsmart Or is this vercel being dumb and in the build of nextjs not allowing an api to b...

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

this

Unsmart•3/2/24, 2:56 AM

I see

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

Unsmart•3/2/24, 3:14 AM

https://github.com/vercel/next.js/pull/36980

Found the PR where they added it lol

GitHub

feat(middleware): issues warnings when using node.js global APIs in...

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

Unsmart•3/2/24, 3:23 AM

lol trying to file an issue on the nextjs repo is way too much effort

luna•3/2/24, 4:16 AM

so that warning just needs to be disabled for next-on-pages, correct?

Unsmart•3/2/24, 4:19 AM

I dont think next-on-pages can modify that at all needs to be fixed on the actual nextjs repo

luna•3/2/24, 4:23 AM

no no i get that. what im asking is, this is supported when deployed correct? (if we get the error removed will it work?)

Unsmart•3/2/24, 4:23 AM

Oh I see, yes it would work when that is removed.

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

in that case i wonder if i can get around this for now with patch-package.

Ffaye Hey, I published a version of nextjs on a cloudflare page using git integration...

faye•3/2/24, 2:30 PM

Could someone help me with this? Would be super greatful :x

faye•3/2/24, 2:37 PM

Running npm run build & npm run start works fine locally for me too

James•3/2/24, 2:46 PM

Can you try redeploying?

JJames Can you try redeploying?

faye•3/2/24, 2:46 PM

I did a lot of times, I changed a lot of the code, nothing helps

faye•3/2/24, 2:47 PM

They 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

faye•3/2/24, 3:09 PM

Even worse: Using npx wrangler pages dev -- npm run startnpx wrangler pages dev -- npm run start also works.. 1crying

faye•3/2/24, 3:53 PM

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

export const runtime = 'edge';

export const metadata = {
  title: 'Forgot password?',
};

export default function Page() {
  return (
      <>
        <h1>Test</h1>
      </>
  );
}

export const runtime = 'edge';

export const metadata = {
  title: 'Forgot password?',
};

export default function Page() {
  return (
      <>
        <h1>Test</h1>
      </>
  );
}

I'm so annoyed about this, why is CF having so many issues with this project?

faye•3/2/24, 3:54 PM

https://github.com/Headpat-Community/web/tree/main/src/app/(main)

It's so empty :(
https://2f0267bb.headpat-web.pages.dev/

I'm managing to get npm run build & turbo build working but I'm running into this issue again with t

Similar Threads