<@545748752892428299> already found a solution? Sounds like Sentry is not enabled in production, pos

@Sam already found a solution? Sounds like Sentry is not enabled in production, possibly due to it not finding the environment variable NEXT_PULBIC_SENTRY_DNS for example. You need to make sure this is available at runtime (in your wrangler.toml or in the dashboard) for potentially SSR and during build time for e.g. static pages (e.g. in your Github CI/CD)

wesbos•1/10/25, 3:48 PM

Is this an OK room to ask questions about opennextjs as well? I dont see a room for it

Wwesbos Is this an OK room to ask questions about opennextjs as well? I dont see a room ...

Victor Berchet•1/10/25, 4:13 PM

There is a dedicated OpenNext Discord, check opennext.js.org

wesbos•1/10/25, 4:13 PM

ah! thank you

James•1/10/25, 6:01 PM

that route uses server functionality and would need to be opted into the edge runtime for next-on-pages

Original message was deleted

Isaac McFadyen•1/10/25, 6:08 PM

The error message you quoted should have the solution right in it.

Isaac McFadyen•1/10/25, 6:08 PM

Is there a reason you can't use edge config for that? It's required, because the client can't get the headers at all (they're a server-side thing).

Original message was deleted

Isaac McFadyen•1/10/25, 6:09 PM

Does one of the packages you are using use async_hooks?

Original message was deleted

James•1/10/25, 6:24 PM

can you post the full build log please

Original message was deleted

James•1/10/25, 6:44 PM

Please can you update to use the latest version of the CLI - I believe your issue might have been fixed in v1.13.6. I will note that your compatibility date will need updating to a date after after Sept 23rd 2024 as well.

Maraciuca•1/12/25, 8:52 PM

hiya, im desperately trying to understand how to use drizzle, hyperdrive and nextjs on edge but i swear im not getting past the env.HYPERDRIVE.connectionString step

has anyone dealt with some like this before?

Vikash•1/13/25, 11:18 AM

I have added runtime = 'edge' on a page, but the CF still complaining that runtime:edgeruntime:edge is missing on unable to build.

Vikash•1/13/25, 11:19 AM

Any suggestion? or the /pages/pages are some sort or reseverd name? as I have /contacts, /users and more pages which passed the build successfully

VVikash I have added runtime = 'edge' on a page, but the CF still complaining that `runt...

D Trombett•1/13/25, 11:39 AM

try adding it in the layout too

DD Trombett try adding it in the layout too

Vikash•1/13/25, 11:41 AM

on root layout?

D Trombett•1/13/25, 11:44 AM

yeah

DD Trombett yeah

Vikash•1/13/25, 11:49 AM

No, again same error

Vikash•1/13/25, 1:33 PM

Renamed “/pages” directory to “/links” and it worked. So it seems CF build script has some bug.

I need to keep the “/pages/[id].tsx” route, so will wait for someone response for a bug fix.

Walshy•1/13/25, 1:35 PM

is the "use client" at the top is overriding the edge runtime?

yags•1/13/25, 7:05 PM

Hello, I'm getting Failed to publish your Function. Got error: Unknown internal error occurredFailed to publish your Function. Got error: Unknown internal error occurred when running npm run deploy. @Walshy I just sent you a DM, hope that's alright!

Yyags Hello, I'm getting `Failed to publish your Function. Got error: Unknown internal...

Walshy•1/13/25, 7:46 PM

In the middle of a few things so a bit delayed atm
error is

Error 8000022: Invalid KV namespace ID (homepage-nonces). Not a valid hex string. Check your KV namespace ID and try again.

Walshy•1/13/25, 7:46 PM

you need the namespace id (hex string) not the name

Hzia•1/14/25, 11:43 AM

Hello, On my localhost I go to my dynamic root for my projects, this works. However if I try to load that same page on my worker page it gives me a Internal Server Error 500? The building and deploying works fine but if I just go to that page it gives me the 500.

It worked 4 months ago but now I pushed an update it doens't anymore?

My cloudflare logs give this:

"Error: No such module \"__next-on-pages-dist__/functions/details/async_hooks\".\n  imported from \"__next-on-pages-dist__/functions/details/[projectId].func.js\""

"Error: No such module \"__next-on-pages-dist__/functions/details/async_hooks\".\n  imported from \"__next-on-pages-dist__/functions/details/[projectId].func.js\""

VVikash Renamed “/pages” directory to “/links” and it worked. So it seems CF build scrip...

James•1/14/25, 9:06 PM

it sounds like Next.js did. It probably thought that pages meant the pages directory and built your app wrong before we got the build output

HHzia Hello, On my localhost I go to my dynamic root for my projects, this works. Howe...

James•1/14/25, 9:06 PM

update to latest version of next on pages and bump your compatibility date

Glib5000•1/15/25, 1:27 AM

I am getting the XMLHttpRequest is not definedXMLHttpRequest is not defined error, but I am not using axios or cross-fetch directly.

This error gets thrown when I call the native

fetch

fetch

outside of a page.tsx file

Glib5000•1/15/25, 1:28 AM

i am using latest version 1.13.71.13.7

Glib5000•1/15/25, 1:29 AM

has anyone experienced this?

Glib5000•1/15/25, 1:47 AM

a lot of people suggest to downgrade to an older version, but then I get the async_hooks error

IItsWendell <@545748752892428299> already found a solution? Sounds like Sentry is not enable...

Sam•1/15/25, 2:52 AM

Nope, not fixed it. We're setting dsndsn in the config and went through the wizard to set it up so you'd think that we'd be ok

It's weird that we're seeing some errors and not others. We've not quota or anything. I'm talking with Sentry support at the moment on it. Hopefully we can work it out.

JJames it sounds like Next.js did. It probably thought that pages meant the pages direc...

Vikash•1/15/25, 6:55 AM

So, what can I change to make it work? My app needs the /pages routes should work.

/app
  /pages
    /[id]
      page.tsx

/app
  /pages
    /[id]
      page.tsx

Also the local build is working fine -

Vikash•1/15/25, 7:09 AM

JJames update to latest version of next on pages and bump your compatibility date

Hzia•1/15/25, 7:53 AM

I upgraded to Nextjs 15 and now i get this error about my Nodejs on cloudflare being out of date:

You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.

You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.

How would i upgrade this version?

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

ItsWendellOP•1/15/25, 8:06 AM

Node is how some of the back-end / CLI javascript is run, to upgrade this it depends on your operating system, node has on their website nice steps you can follow to download / upgrade: https://nodejs.org/en/download

Node.js — Download Node.js®

Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.

D Trombett•1/15/25, 8:24 AM

They probably want to upgrade the cloudflare version

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

D Trombett•1/15/25, 8:25 AM

Create a .node-version.node-version file in the root directory and write the version in it, like 22.12.022.12.0

DD Trombett Create a `.node-version` file in the root directory and write the version in it,...

Hzia•1/15/25, 8:27 AM

i did it with a env var in cloudflare,

Error: ENOENT: no such file or directory, lstat '/opt/buildhome/repo/.next/server/app/favicon.ico/route_client-reference-manifest.js'

Error: ENOENT: no such file or directory, lstat '/opt/buildhome/repo/.next/server/app/favicon.ico/route_client-reference-manifest.js'

this error comes up instead now

JJames update to latest version of next on pages and bump your compatibility date

Hzia•1/15/25, 11:10 AM

I changed from nextjs 15 canary to 15.1.4 and now i still get this error?

"Error: No such module \"__next-on-pages-dist__/functions/details/async_hooks\".\n  imported from \"__next-on-pages-dist__/functions/details/[projectId].func.js\""

"Error: No such module \"__next-on-pages-dist__/functions/details/async_hooks\".\n  imported from \"__next-on-pages-dist__/functions/details/[projectId].func.js\""

Hzia•1/15/25, 11:15 AM

ah wait nvm, i forgot compatibility date..

Hzia•1/15/25, 11:15 AM

works now

Alex Oliveira•1/15/25, 11:03 PM

I created a route to generate several static pages from the "domain" parameter, so I used "generateStaticParams".

I already received an error saying that I cannot use "generateStaticParams" together with "export const runtime = 'edge';"

but if I remove the "export const runtime = 'edge';" I get an error saying that I need to put it in the dynamic routes.

How should I solve this dilemma?

Alex Oliveira•1/15/25, 11:53 PM

this helped me:
https://github.com/cloudflare/next-on-pages/issues/833

GitHub

[🐛 Bug]: Failed to generate SSG dynamic routes due to Vercel CLI br...

next-on-pages environment related information System: Platform: linux Arch: x64 Shell: /bin/bash Package Manager Used: npm (10.7.0) Relevant Packages: @cloudflare/next-on-pages: 1.12.1 verc...

Original message was deleted

Hello, I’m Allie!•1/17/25, 5:08 AM

?abuse

SuperHelpflare•1/17/25, 5:08 AM

If you feel that a site is engaging in illegal or inappropriate activities, you can submit an abuse report at https://abuse.cloudflare.com/. The Trust and Safety team will review the details and reply if appropriate. You can also report the site to your relevant local authorities. Reports cannot be filed via Discord or with individual employees or Champs.

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

Hello, I am stuck on a problem for days. Trying to deploy a large Nextjs project. Clould some help me debug the issue Ever since I slove one issue it comes up with a few more

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

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

Build runs successfully, but when I try to access the webpage it throws this error. I am not sure how to locate the file which is causing these errors

Monty•1/17/25, 10:09 AM

✘ [ERROR] Error: Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope. To fix this error, perform this operation within a handler. https://developers.cloudflare.com/workers/runtime-apis/handlers/

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

How can I locate the actual files, the errors shown are from the build files which are minified :>

James•1/17/25, 11:42 AM

if you look at the .vercel/output/_worker.js/nop-build-info.json (or something like that) it should tell you which chunks are for which page file if i recall correctly

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?

<@545748752892428299> already found a solution? Sounds like Sentry is not enabled in production, pos

Similar Threads

Similar Threads

Similar Threads