if you look at the .vercel/output/_worker.js/nop-build-info.json (or something like that) it should

S

sean.h•1/17/25, 3:47 PM

Hi all,

I've seen some strange behaviour with environment variables on a Pages project that's using next-on-pages.

If I set variables via the Cloudflare dashboard, they show as part of the deployment which is triggered by a direct upload using the cloudflare/wrangler-action@v3 GitHub action. However after adding a page that outputs process.env they're not included in the output, lots of other environment variables are, so the output isn't empty.

If I set environment variables at the step level of a GitHub actions workflow, these are also not carrying through to the deployment.

If I set environment variables at the top level of a GitHub actions workflow, these are carried through to the deployment.

Has anyone else seen similar behaviour?

HHzia I upgraded to Nextjs 15 and now i get this error about my Nodejs on cloudflare b...

C

charl.dev•1/17/25, 8:55 PM

this also tripped me up, tried

.nvmrc

.nvmrc

.nvmrc

.nvmrc and setting env var (via dash

/pages/view/browserid-dash/settings/production#variables

/pages/view/browserid-dash/settings/production#variables

/pages/view/browserid-dash/settings/production#variables

/pages/view/browserid-dash/settings/production#variables) for NODE_VERSION=22.13.0 and still getting errors.

This is with a fresh next-on-pages and deploying via gitgub

Looks like env var not respected and

.nvmrc

.nvmrc

.nvmrc

.nvmrc throws:

HEAD is now at 58fd0e5 Update .nvmrc
22:12:31.380    
22:12:31.455    
22:12:31.455    Using v2 root directory strategy
22:12:31.475    Success: Finished cloning repository files
22:12:32.897    Checking for configuration in a Wrangler configuration file (BETA)
22:12:32.898    
22:12:32.898    Found wrangler.json file. Reading build configuration...
22:12:32.905    pages_build_output_dir: .vercel/output/static
22:12:32.905    Build environment variables: (none found)
22:12:33.001    Successfully read wrangler.toml file.
22:12:34.091    Detected the following tools from environment: nodejs@NODE_VERSION=18.18.0, npm@9.6.7
22:12:34.091    Installing nodejs NODE_VERSION=18.18.0
22:12:34.608    Trying to update node-build... ok
22:12:34.641    node-build: definition not found: node_version=18.18.0
22:12:34.648    Error: Exit with error code: 1
22:12:34.648        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
22:12:34.648        at Object.onceWrapper (node:events:652:26)
22:12:34.648        at ChildProcess.emit (node:events:537:28)
22:12:34.648        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
22:12:34.657    Failed: build command exited with code: 1
22:12:35.428    Failed: error occurred while running build command

HEAD is now at 58fd0e5 Update .nvmrc
22:12:31.380    
22:12:31.455    
22:12:31.455    Using v2 root directory strategy
22:12:31.475    Success: Finished cloning repository files
22:12:32.897    Checking for configuration in a Wrangler configuration file (BETA)
22:12:32.898    
22:12:32.898    Found wrangler.json file. Reading build configuration...
22:12:32.905    pages_build_output_dir: .vercel/output/static
22:12:32.905    Build environment variables: (none found)
22:12:33.001    Successfully read wrangler.toml file.
22:12:34.091    Detected the following tools from environment: nodejs@NODE_VERSION=18.18.0, npm@9.6.7
22:12:34.091    Installing nodejs NODE_VERSION=18.18.0
22:12:34.608    Trying to update node-build... ok
22:12:34.641    node-build: definition not found: node_version=18.18.0
22:12:34.648    Error: Exit with error code: 1
22:12:34.648        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
22:12:34.648        at Object.onceWrapper (node:events:652:26)
22:12:34.648        at ChildProcess.emit (node:events:537:28)
22:12:34.648        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
22:12:34.657    Failed: build command exited with code: 1
22:12:35.428    Failed: error occurred while running build command

HEAD is now at 58fd0e5 Update .nvmrc
22:12:31.380    
22:12:31.455    
22:12:31.455    Using v2 root directory strategy
22:12:31.475    Success: Finished cloning repository files
22:12:32.897    Checking for configuration in a Wrangler configuration file (BETA)
22:12:32.898    
22:12:32.898    Found wrangler.json file. Reading build configuration...
22:12:32.905    pages_build_output_dir: .vercel/output/static
22:12:32.905    Build environment variables: (none found)
22:12:33.001    Successfully read wrangler.toml file.
22:12:34.091    Detected the following tools from environment: nodejs@NODE_VERSION=18.18.0, npm@9.6.7
22:12:34.091    Installing nodejs NODE_VERSION=18.18.0
22:12:34.608    Trying to update node-build... ok
22:12:34.641    node-build: definition not found: node_version=18.18.0
22:12:34.648    Error: Exit with error code: 1
22:12:34.648        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
22:12:34.648        at Object.onceWrapper (node:events:652:26)
22:12:34.648        at ChildProcess.emit (node:events:537:28)
22:12:34.648        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
22:12:34.657    Failed: build command exited with code: 1
22:12:35.428    Failed: error occurred while running build command

HEAD is now at 58fd0e5 Update .nvmrc
22:12:31.380    
22:12:31.455    
22:12:31.455    Using v2 root directory strategy
22:12:31.475    Success: Finished cloning repository files
22:12:32.897    Checking for configuration in a Wrangler configuration file (BETA)
22:12:32.898    
22:12:32.898    Found wrangler.json file. Reading build configuration...
22:12:32.905    pages_build_output_dir: .vercel/output/static
22:12:32.905    Build environment variables: (none found)
22:12:33.001    Successfully read wrangler.toml file.
22:12:34.091    Detected the following tools from environment: nodejs@NODE_VERSION=18.18.0, npm@9.6.7
22:12:34.091    Installing nodejs NODE_VERSION=18.18.0
22:12:34.608    Trying to update node-build... ok
22:12:34.641    node-build: definition not found: node_version=18.18.0
22:12:34.648    Error: Exit with error code: 1
22:12:34.648        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
22:12:34.648        at Object.onceWrapper (node:events:652:26)
22:12:34.648        at ChildProcess.emit (node:events:537:28)
22:12:34.648        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
22:12:34.657    Failed: build command exited with code: 1
22:12:35.428    Failed: error occurred while running build command

Any ideas?

Ssean.h Hi all, I've seen some strange behaviour with environment variables on a Pages ...

J

JamesOP•1/17/25, 10:18 PM

I can't say I've heard of this before, but I wonder whether the page is getting prerendered instead of SSRd

R

rrandom2236•1/18/25, 6:25 AM

can anybody help me with this issue https://github.com/cloudflare/next-on-pages/issues/934

GitHub

[🐛 Bug]: Unable to call Service binding in a route handler · Issue ...

next-on-pages environment related information unable to run npx @cloudflare/next-on-pages --info Description In a POST handler, I call the service bing of another worker, failed export async functi...

JJames if you look at the .vercel/output/_worker.js/nop-build-info.json (or something l...

M

Monty•1/18/25, 1:52 PM

Thanks @James, it's a large json file. Does it contain any object or entry which indicates the defected part?

MMonty Thanks <@94508156243161088>, it's a large json file. Does it contain any object ...

J

JamesOP•1/18/25, 5:52 PM

If you search for the name of the webpack chunk file that you see in the error, you should see all the places where that chunk is used

D

Dev•1/21/25, 6:24 AM

Has anyone tried cf-d1 with drizzle-orm in nextjs?

M

majestic•1/21/25, 7:04 AM

How do you guys developing next dynamic router on pages, using runtime = 'edge' ?

M

Monty•1/21/25, 10:03 AM

Hello, I am deplying my Nextjs app on Cloudflare pages, the dynamic pages with SSR work fine but as I integrate Wagmi (Web3) libraray into the project which wraps the whole app as global configuration. Afterwards I am not able to use fetch or axios to make API requests. Following are the error details:

✘ [ERROR] ReferenceError: XMLHttpRequest is not defined @James

M

Monty•1/21/25, 10:03 AM

Please note that I have enabled SSR into the Wagmi config, this behaviour is only with Cloudflare pages deployment

Mmajestic How do you guys developing next dynamic router on pages, using runtime = 'edge' ...

M

Monty•1/21/25, 10:05 AM

export const runtime = "edge";

add this line into your dynamic page file, if this is what you are asking?

M

majestic•1/21/25, 10:07 AM

Yes but when i add this line of code build fails on Deployment command

M

Monty•1/21/25, 10:07 AM

Did you try local dev and build?

M

Monty•1/21/25, 10:08 AM

Can you show me the error?

M

majestic•1/21/25, 10:12 AM

M

Monty•1/21/25, 10:13 AM

Did you try Yarn?

M

majestic•1/21/25, 10:14 AM

yes i tried yarn and bun

M

majestic•1/21/25, 10:15 AM

Can you please share your photo or code of using dynamic router page code ?

M

Monty•1/21/25, 10:16 AM

sure

M

Monty•1/21/25, 10:16 AM

@majestic

M

majestic•1/21/25, 10:24 AM

can you please show me next version and deployment command ?

M

Monty•1/21/25, 10:28 AM

the local dev command is:

npx wrangler pages dev

npx wrangler pages dev

npx wrangler pages dev

npx wrangler pages dev

and the command for build is

npx @cloudflare/next-on-pages

npx @cloudflare/next-on-pages

npx @cloudflare/next-on-pages

npx @cloudflare/next-on-pages

"pages:dev": "npx wrangler pages dev",
"pages:build": "npx @Cloudflare/next-on-pages",
"preview": "npm run pages:build && wrangler pages dev",
"deploy": "npm run pages:build && wrangler pages deploy"

Have you created wranger.tmol file?

M

majestic•1/21/25, 10:30 AM

Yes i deployed it successfully but when i added dynamic routing and also that file includes line of edge, its failing to build

Original message was deleted

H

Hello, I’m Allie!•1/22/25, 3:22 PM

?crossposting

S

SuperHelpflare•1/22/25, 3:22 PM

Please do not post your question in multiple channels/post it multiple times per the rules at No Access. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

J

JamesOP•1/22/25, 4:34 PM

Are you on the free plan?

J

JamesOP•1/22/25, 4:35 PM

I believe Workers Free has a 10ms limit which will not be sufficient for Next.js

K

kchro3•1/22/25, 9:54 PM

I have a question about NextJS on Pages. Is it like workers where there is a concurrency limit of 6 outgoing requests at a time?

Kkchro3 I have a question about NextJS on Pages. Is it like workers where there is a con...

H

Hard@Work•1/22/25, 9:57 PM

Yes, since Pages runs on Workers too

Q

Qalib•1/23/25, 12:34 PM

hey guys, we have reached the limit of Pages Functions bundle size of 25Mib, which prevents us from releasing new features on Cloudflare Pages and blocks the development process. We have requested a limit increase last week, but didn't get a reply. Is there a way to increase this limit?
We are using CF pages Paid plan + Pro plan
Account ID: a8ca576f8d052ec304f234b76fa71044
Deployment ID: 1582ba91-a2f8-4cd4-bd91-0dadf991771e

J

JamesOP•1/23/25, 2:19 PM

I believe 25mb is a hard limit, i.e. can't go above

J

JamesOP•1/23/25, 2:20 PM

You should try and see if there are areas of your app that can be optimized to reduce the bundle size, because 25mb (after deduplication etc.) sounds very big

JJames I believe 25mb is a hard limit, i.e. can't go above

H

Hello, I’m Allie!•1/23/25, 2:20 PM

Isn’t that for Assets, not Functions?

HHello, I’m Allie!Isn’t that for Assets, not Functions?

J

JamesOP•1/23/25, 2:20 PM

¯\_(ツ)_/¯

J

JamesOP•1/23/25, 2:21 PM

That's just what I remember being told a while ago

HHello, I’m Allie!Isn’t that for Assets, not Functions?

Q

Qalib•1/23/25, 2:25 PM

yup, that's what i thought as well

JJames I believe 25mb is a hard limit, i.e. can't go above

W

Walshy•1/23/25, 3:35 PM

this.

D

dex•1/23/25, 4:13 PM

is there a place where i can seew hich nextjs version is compatible with pages?

D

dex•1/23/25, 4:13 PM

which latest next version i mean

J

JamesOP•1/23/25, 5:22 PM

Only Next.js 14 is officially supported, but I believe people have got Next.js 15 working as well

M

makisuo•1/25/25, 11:48 PM

I'm also having soem size issue, but at this point have nothing more to optimize it feels like... all dependencies are required. But the page size is keep growing with every new page we add and we are very close to the 25mb again. Are we doing something wrong here?

blocks-getjustd-com.a5358b05-d6b7-4319-a5b7-43bf7978fb98.log118.79KB

D

Dev•1/26/25, 12:59 PM

does resend email work with next-on-pages?
im getting this error

✘ [ERROR] Failed to send email: ReferenceError: MessageChannel is not defined

✘ [ERROR] Failed to send email: ReferenceError: MessageChannel is not defined

✘ [ERROR] Failed to send email: ReferenceError: MessageChannel is not defined

✘ [ERROR] Failed to send email: ReferenceError: MessageChannel is not defined when called the email sending server action

D

Dev•1/26/25, 12:59 PM

if it does not, whats the next best method to send email from a cloudflare environment

Mmakisuo I'm also having soem size issue, but at this point have nothing more to optimize...

J

JamesOP•1/26/25, 4:17 PM

109 edge function routes is a heck of a lot. The deduping of webpack chunks is helping massively already taking each route from 600-650kb to 140-180kb. i think you're running into the limit purely just because you have so many routes

Y

Yomisana•1/26/25, 4:21 PM

Hi I have issue about build v2 nodejs version is

18.17.1

18.17.1

18.17.1

18.17.1 issue about latest nextjs need

18.18.0

18.18.0

18.18.0

18.18.0
using command create nextjs app of

npm create cloudflare@latest -- my-next-app --framework=next

npm create cloudflare@latest -- my-next-app --framework=next

npm create cloudflare@latest -- my-next-app --framework=next

npm create cloudflare@latest -- my-next-app --framework=next
Cloudflare docs

Cloudflare Docs

Get started | Full-stack (SSR) | Next.js apps · Cloudflare Pages docs

Deploy a full-stack Next.js app to Cloudflare Pages

YYomisana Hi I have issue about build v2 nodejs version is ``18.17.1`` issue about latest ...

I

Isaac McFadyen•1/26/25, 4:23 PM

Set an environment variable (in the Pages settings) of

NODE_VERSION

NODE_VERSION

NODE_VERSION

NODE_VERSION and a value of

20

JJames 109 edge function routes is a heck of a lot. The deduping of webpack chunks is h...

M

makisuo•1/26/25, 4:25 PM

We just have a lot of routes yeah.
I have everything as edge runtime right now preventing some of the routes that could be statically rendered to be static.

But as far as i understood it, thats kinda the limitation here. Does this just mean next on pages has a "soft route limit"?

IIsaac McFadyen Set an environment variable (in the Pages settings) of `NODE_VERSION` and a valu...

Y

Yomisana•1/26/25, 4:26 PM

still failed

YYomisana still failed

I

Isaac McFadyen•1/26/25, 4:27 PM

What does the error say in the logs?

if you look at the .vercel/output/_worker.js/nop-build-info.json (or something like that) it should

Similar Threads

Similar Threads

Similar Threads