It is recommended you use Linux or MacOS As per the docs - [link](https://github.com/cloudflare/nex

Ccj It is recommended you use Linux or MacOS As per the docs - [link](https://githu...

R

ronit•6/5/24, 7:55 AM

ohh cool!! Thanks @cj

A

arunvilliers17•6/6/24, 7:09 AM

we have deployed our website in pages and it is working fine in pages dynamic URL, After mapping a custom domain to the dynamic URL. website static page is getting loaded, but the dynamic pages are not getting loaded.

Aarunvilliers17 we have deployed our website in pages and it is working fine in pages dynamic UR...

C

cjOP•6/6/24, 3:48 PM

Do you mean dynamic routes ?

What I understand is:

Your next js app works in production with a url like this
```
https://project-name.pages.dev/
```
https://project-name.pages.dev/
```
https://project-name.pages.dev/
```
https://project-name.pages.dev/
, right?
You added a custom domain for this project - cool

Now what is the problem?

https://project-name.pages.dev/

https://project-name.pages.dev/

https://project-name.pages.dev/

https://project-name.pages.dev/ works, but

project-name.com

project-name.com

project-name.com

project-name.com does not?

S

sszsssszs•6/7/24, 5:19 AM

Hi there, I would like to add _middleware.js for the new next.js project. Could someone help to explain where should I put this file?

Ccj Do you mean [dynamic routes](https://nextjs.org/docs/pages/building-your-applica...

A

arunvilliers17•6/7/24, 5:35 AM

yes, i mention my url

pages url: dev-poorvika-ecom.pages.dev
custom domain: https://dev-cf.poorvika.com/

kindly check this url

Best Online Shopping for Mobiles, Laptops, Home Appliances & more in India

Ssszsssszs Hi there, I would like to add _middleware.js for the new next.js project. Could ...

C

cjOP•6/7/24, 8:11 AM

If you have a

src

src

src

src folder then inside that. Else place it at the root of the project - docs

/
  src/
    app/
    - middleware.ts

/
  src/
    app/
    - middleware.ts

/
  src/
    app/
    - middleware.ts

/
  src/
    app/
    - middleware.ts

else

/
  app/
  - middleware.ts

/
  app/
  - middleware.ts

/
  app/
  - middleware.ts

/
  app/
  - middleware.ts

Aarunvilliers17 yes, i mention my url pages url: dev-poorvika-ecom.pages.dev custom domain: htt...

C

cjOP•6/7/24, 8:22 AM

Hm, I don't know what the issue might be here without access to the code. Please try doing the following

Check if the production build works locally
Try creating a minimal reproducible example and post a question on pages-help

A

AA•6/7/24, 5:04 PM

https://github.com/cloudflare/next-on-pages/blob/c2b173ce89c82dd1566474191691bb5d62d01e67/packages/next-on-pages/templates/_worker.js/utils/fetch.ts#L20 <-- somehow i have an outbound POST request thats getting cached and its not making a lot of sense

GitHub

next-on-pages/packages/next-on-pages/templates/_worker.js/utils/fet...

CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages

VVillage (Josef)Or restructure into a monorepo

R

Rohit Verma•6/9/24, 6:28 AM

hey, did you find any solution or you are trying with restructuring

V

Village (Josef)•6/9/24, 4:57 PM

Haven’t found anything nope

V

Village (Josef)•6/9/24, 4:58 PM

Probably going to end up having to restructure into a Pages app, cron worker, and shared utilities

VVillage (Josef)Probably going to end up having to restructure into a Pages app, cron worker, an...

H

Hello, I’m Allie!•6/9/24, 5:02 PM

This. Pages itself does not support any handlers other than fetch, so Crons have to be in a separate Worker

V

Village (Josef)•6/9/24, 5:36 PM

Sigh aw well

V

Village (Josef)•6/9/24, 5:36 PM

Thanks!

V

Village (Josef)•6/11/24, 1:46 AM

For some reason R2 just flat out doesn't work anymore. My production code (same code) works just fine, but when I attempt to pass in Headers objects to portions of r2.get or object.writeHttpMetadata, as is supported or at least was, it errors out with cannot stringify arbitrary non-POJO's. Then, if I remove all usage of that, the instant r2.get returns an object the body is read already so it's impossible for me to actually read what's inside the object and do anything with it.

V

Village (Josef)•6/11/24, 1:46 AM

Is this a known issue or something new or?

V

Village (Josef)•6/11/24, 1:46 AM

Like R2 just flat out doesn't work locally anymore which isn't the greatest

JJames Yes generateStaticParams is supposed to be used for SSGing routes at build time

S

Soren•6/11/24, 8:13 PM

generateStaticParams

generateStaticParams

generateStaticParams

generateStaticParams doesn't work on cloudflare, no?

SSoren `generateStaticParams` doesn't work on cloudflare, no?

J

James•6/11/24, 9:14 PM

it tells you in the next sentence how you can use it

JJames it tells you in the next sentence how you can use it

S

Soren•6/11/24, 9:20 PM

Now I get it. Dang. And btw does

/api

/api

/api

/api route work on Cloudflare? Or will it break?

This is my

api/revalidate/route.ts

api/revalidate/route.ts

api/revalidate/route.ts

api/revalidate/route.ts

import { NextRequest, NextResponse } from "next/server";
import { getPosts } from "@/utils/apis";

export const GET = async (req: NextRequest) => {
    try {
        const posts = await getPosts();
        return NextResponse.json(posts, {status: 200});
    } catch (err: any) {
        return NextResponse.json({error: err.message}, {status: 500});
    }
};

import { NextRequest, NextResponse } from "next/server";
import { getPosts } from "@/utils/apis";

export const GET = async (req: NextRequest) => {
    try {
        const posts = await getPosts();
        return NextResponse.json(posts, {status: 200});
    } catch (err: any) {
        return NextResponse.json({error: err.message}, {status: 500});
    }
};

import { NextRequest, NextResponse } from "next/server";
import { getPosts } from "@/utils/apis";

export const GET = async (req: NextRequest) => {
    try {
        const posts = await getPosts();
        return NextResponse.json(posts, {status: 200});
    } catch (err: any) {
        return NextResponse.json({error: err.message}, {status: 500});
    }
};

import { NextRequest, NextResponse } from "next/server";
import { getPosts } from "@/utils/apis";

export const GET = async (req: NextRequest) => {
    try {
        const posts = await getPosts();
        return NextResponse.json(posts, {status: 200});
    } catch (err: any) {
        return NextResponse.json({error: err.message}, {status: 500});
    }
};

SSoren Now I get it. Dang. And btw does `/api` route work on Cloudflare? Or will it bre...

N

Nob•6/12/24, 1:49 AM

add export const runtime = 'edge'

S

Soren•6/12/24, 1:52 AM

Do I need to add it in every file? @Nob

G

gerbyzation•6/12/24, 10:52 AM

Is it possible to turn off minification somehow? Attempting to port an existing next app over to cloudflare pages but we're running into some issues and it's not clear where this is originating from

✘ [ERROR] TypeError: Invalid URL string.

      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:3608)
      at Mt
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:2452)
      at os.request
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:5643)
      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:641)
      at qs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:17)
      at GetNavigation
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:634)
      at Vs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:960)
      at Hs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:503:343)
      at qe
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/webpack/7918f84a91933fd88af2d7a37e95066f.js:5:501)
      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/webpack/7918f84a91933fd88af2d7a37e95066f.js:9:7888)

✘ [ERROR] TypeError: Invalid URL string.

      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:3608)
      at Mt
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:2452)
      at os.request
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:5643)
      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:641)
      at qs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:17)
      at GetNavigation
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:634)
      at Vs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:960)
      at Hs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:503:343)
      at qe
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/webpack/7918f84a91933fd88af2d7a37e95066f.js:5:501)
      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/webpack/7918f84a91933fd88af2d7a37e95066f.js:9:7888)

✘ [ERROR] TypeError: Invalid URL string.

      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:3608)
      at Mt
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:2452)
      at os.request
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:5643)
      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:641)
      at qs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:17)
      at GetNavigation
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:634)
      at Vs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:960)
      at Hs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:503:343)
      at qe
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/webpack/7918f84a91933fd88af2d7a37e95066f.js:5:501)
      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/webpack/7918f84a91933fd88af2d7a37e95066f.js:9:7888)

✘ [ERROR] TypeError: Invalid URL string.

      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:3608)
      at Mt
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:2452)
      at os.request
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:77:5643)
      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:641)
      at qs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:17)
      at GetNavigation
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:634)
      at Vs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:492:960)
      at Hs
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/functions/[lang].func.js:503:343)
      at qe
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/webpack/7918f84a91933fd88af2d7a37e95066f.js:5:501)
      at null.<anonymous>
  (file:///Users/gerbenneven/projects/pages-test-project/.vercel/output/static/_worker.js/__next-on-pages-dist__/webpack/7918f84a91933fd88af2d7a37e95066f.js:9:7888)

SSoren Do I need to add it in every file? <@1048398696460599357>

N

Nob•6/12/24, 11:52 AM

yes for every page/api that should run on the edge

N

Nob•6/12/24, 11:53 AM

api should always run on the edge

SSoren Do I need to add it in every file? <@1048398696460599357>

I

ItsWendell•6/13/24, 8:01 AM

Actually, just adding it to the root layout worked fine for us, but we don't use API endpoints but a binding to an actual worker.

Ggerbyzation Is it possible to turn off minification somehow? Attempting to port an existing ...

I

ItsWendell•6/13/24, 8:08 AM

This error means that somewhere within your SSR code you're probably passing a relative path to an URL constructor

Ggerbyzation Is it possible to turn off minification somehow? Attempting to port an existing ...

J

James•6/13/24, 10:35 AM

--disable-worker-minification

--disable-worker-minification

--disable-worker-minification

--disable-worker-minification

JJames `--disable-worker-minification`

G

gerbyzation•6/13/24, 11:29 AM

Where do you pass this to? Google shows 0 results searching for this option

G

gerbyzation•6/13/24, 11:32 AM

Ah sourcegraph is a lifesaver, found it: https://sourcegraph.com/github.com/cloudflare/next-on-pages/-/blob/packages/next-on-pages/src/cli.ts?L47

cli.ts?L47

G

gerbyzation•6/13/24, 11:35 AM

Are there any tricks to catch uncaught errors, ideally globally somewhere? Some errors don't come with stack traces at all, which makes it a nightmare to track down where they might come from

✘ [ERROR] Uncaught (async) Error: internal error

✘ [ERROR] Uncaught (async) Error: internal error

✘ [ERROR] Uncaught (async) Error: internal error

✘ [ERROR] Uncaught (async) Error: internal error

J

James•6/13/24, 12:02 PM

internal errors means something went wrong inside cloudflare pages/workers

JJames internal errors means something went wrong inside cloudflare pages/workers

G

gerbyzation•6/13/24, 1:16 PM

Yeah, but most likely because of some bad input? With the non-descript error + no stack trace it's a needle in a haystack problem. We dumped a ton of try/catch into our app and eventually found something. In a worker it's a bit easier to debug as you can just wrap at the entrypoint and catch any uncaught errors

J

James•6/13/24, 1:18 PM

its something going legitimately wrong on cloudflare's end if you get just 'Error: internal error', you will normally need an employee to check if they can see something for the deployment id

G

gerbyzation•6/13/24, 1:19 PM

Hmm okay, is there anything we can check if this happens locally running with wrangler/workerd?

JJames its something going legitimately wrong on cloudflare's end if you get just 'Erro...

G

gerbyzation•6/13/24, 1:21 PM

We're just running this locally while trying to get it working, haven't setup any deployments yet

J

James•6/13/24, 1:54 PM

maybe something throwing an exception in workerd locally

JJames maybe something throwing an exception in workerd locally

G

gerbyzation•6/13/24, 1:58 PM

Nothing visible in the output. I'll hit up our cloudflare support contacts to see if we can get someone from CF to take a look. Thanks for your help!

R

Ronan Berder•6/14/24, 2:02 AM

Has anyone done work to optimize the bundle size of their Next.js build?

R

Ronan Berder•6/14/24, 2:03 AM

With the App Router, it seems that pretty much everything gets bundled together, regardless of whether it's client or server side.

S

Sumiya•6/14/24, 8:49 AM

Hello everyone, Do you guys build nextjs pages project using nx project.json?

F

Flox•6/14/24, 1:12 PM

Hey does someone have a good idea for how to set up your API_URL environment variables?

I am currently setting them in my wrangler.toml file and then using getRequestContext().env.API_URL to access them. This works both locally and in deployment for my functions in api/route/..

However when i try to access my apis at ”api/route” (using fetch in my page.tsx component) it works locally but seems to break in production:/

Thanks for any respons!

A

astrid•6/14/24, 2:09 PM

Is there any way to make some built-in environment variables public?

I'm trying to access

CF_PAGES_BRANCH

CF_PAGES_BRANCH

CF_PAGES_BRANCH

CF_PAGES_BRANCH &

CF_PAGES_URL

CF_PAGES_URL

CF_PAGES_URL

CF_PAGES_URL within a client component for functionality, but I can't seem to access them as

NEXT_PUBLIC_*

NEXT_PUBLIC_*

NEXT_PUBLIC_*

NEXT_PUBLIC_* is not appended.

I've looked into

getRequestContext

getRequestContext

getRequestContext

getRequestContext, but that doesn't seem to work for my usecase, as it's only for server-side code.

UPDATE: The solution is using the env config option to map them to

NEXT_PUBLIC_*

NEXT_PUBLIC_*

NEXT_PUBLIC_*

NEXT_PUBLIC_* variables.

Z

zerushinho•6/14/24, 5:03 PM

Hello everyone, everything ok?

I'm working on a project with nextjs 14 and when I upload the project to cloudflare pages. Only one page works in SSR. The others do not load the fetch. Has anyone had this problem and know how to solve it?

DDeleted User i am also getting random 500 error in my next-on-pages , i am also using default...

J

James•6/14/24, 5:24 PM

do you get any errors in your deployment logs?

It is recommended you use Linux or MacOS As per the docs - [link](https://github.com/cloudflare/nex

Similar Threads