is that something known orrr

N

neoneyOP•6/15/24, 8:45 PM

and the last time i had this happen i solved it by...

N

neoneyOP•6/15/24, 8:45 PM

randomly renaming the files it was happening in

N

neoneyOP•6/15/24, 8:46 PM

changing the functions a bit...

N

neoneyOP•6/15/24, 8:46 PM

so idk

N

neoneyOP•6/15/24, 8:47 PM

and it works completely fine in next dev mode

N

neoneyOP•6/15/24, 8:48 PM

but does error in preview

N

neoneyOP•6/15/24, 8:48 PM

with the exact same chunk name

HHello, I’m Allie!> If you are on the Pro, Business, or Enterprise plan you can customize and bran...

A

Abdoulaye•6/16/24, 1:17 AM

Thanks

N

Nooc•6/16/24, 5:09 AM

hello, I'm building a blog website using NextJs with Cloudflare and next-on-pages. Because the blog has so many images, so it is easy to reach the size limit of Cloudflare Worker. Can you tell me how to avoid this limitation? Such as, how to exclude the static assets like images and fonts to count in Cloudflare Worker size limit.

NNooc hello, I'm building a blog website using NextJs with Cloudflare and next-on-page...

J

James•6/16/24, 10:20 AM

You can make a custom _routes.json file in your project for your images/fonts etc. and we'll merge it with the one that gets made in the output directory

Nneoney is that something known orrr

J

James•6/16/24, 10:20 AM

can you make an issue with a repro

N

neoneyOP•6/18/24, 10:56 PM

not really

N

neoneyOP•6/19/24, 7:56 AM

seems to be a nextjs issue

N

neoneyOP•6/19/24, 7:56 AM

anyway, can I make an R2 binding I have upload to the live binding in dev mode?

Nneoney anyway, can I make an R2 binding I have upload to the live binding in dev mode?

H

Hello, I’m Allie!•6/19/24, 8:06 AM

IIRC Pages dev is local-only

N

neoneyOP•6/19/24, 9:06 AM

alright

Z

Zeeshan•6/20/24, 4:12 AM

Has anyone got hono+nextjs+d1 working together? i want to use this stack and deploy on cloudflare pages but wanted to know if i will jump into any bottlenecks so i can be aware of.

P

Phonebox•6/21/24, 4:42 AM

functions

FFredthedoggy Is it within the logs section of the real time report on the functions dashboard...

I

ixixix•6/23/24, 4:53 AM

yes

I

ixixix•6/23/24, 4:53 AM

workers & pages -> <your project> -> view details -> functions -> scroll down to “begin log stream” https://developers.cloudflare.com/pages/functions/debugging-and-logging/#view-logs-in-the-cloudflare-dashboard

Cloudflare Docs

Debugging and logging · Cloudflare Pages docs

Access your Functions logs by using the Cloudflare dashboard or the Wrangler CLI.

DDeleted User Cloudflare webhook is being called multiple times, and builds are being created ...

I

Isaac McFadyen•6/25/24, 5:17 PM

If the webhook is being called multiple times then it's the responsibility of whatever is calling the webhook to not call it multiple times.

I

Isaac McFadyen•6/25/24, 5:18 PM

Triggering multiple builds when called multiple times is intended behavior, it wouldn't make sense to just ignore webhook calls.

K

konsumer•6/25/24, 10:57 PM

Hi, I am trying to use DO-bindings that otherwise work on normal workers:

[[durable_objects.bindings]]
name = "STORE"
class_name = "StoreDurableObject"
script_name = "store-main"

[[durable_objects.bindings]]
name = "STORE"
class_name = "StoreDurableObject"
script_name = "store-main"

[[durable_objects.bindings]]
name = "STORE"
class_name = "StoreDurableObject"
script_name = "store-main"

[[durable_objects.bindings]]
name = "STORE"
class_name = "StoreDurableObject"
script_name = "store-main"

I generally use

--remote

--remote

flag to use them directly. I am trying to do this on

@cloudflare/next-on-pages

@cloudflare/next-on-pages

@cloudflare/next-on-pages

@cloudflare/next-on-pages and it gives me error

[wrangler] Couldn't find `wrangler dev` session for class "StoreDurableObject" to proxy to

[wrangler] Couldn't find `wrangler dev` session for class "StoreDurableObject" to proxy to

[wrangler] Couldn't find `wrangler dev` session for class "StoreDurableObject" to proxy to

[wrangler] Couldn't find `wrangler dev` session for class "StoreDurableObject" to proxy to

Is there a way to configure it (maybe in

setupDevPlatform

setupDevPlatform

?) to use remote proxying like with normal

wrangler dev

wrangler dev

? If I have to make my own local copy that sends remote requests, I can do that too, but I am not sure how to add

StoreDurableObject

StoreDurableObject

StoreDurableObject

StoreDurableObject proxy-class to worker (since it's all wrapped up in next)

K

konsumer•6/25/24, 11:03 PM

the DO itself is a graphql server, and I have it exposed in a http worker, so hitting it remote is totally an option on local dev (make a

StoreDurableObject

StoreDurableObject

StoreDurableObject

StoreDurableObject that just fetches the remote http) but it would be cool if it just used all remote data, like i do in worker-dev (with

--remote

--remote

flag.) It's all working as expected with KV/D1, too, so this is just a DO problem.

K

konsumer•6/25/24, 11:24 PM

I dunno, I might just polyfill it in dev (if it's running local, fetch from remote.) The DO works on remote-deploy, so it seems fine, otherwise, so I could insert it at point where I am using it. it would be nice if there was just a way to specify "use all remote resources" like

wrangler dev --remote

wrangler dev --remote

K

konsumer•6/25/24, 11:51 PM

yeh, this works ok:

 let out

  if (process?.env?.NODE_ENV === 'development') {
    const cookieStore = cookies()
    const idToken = cookieStore.get('idToken')?.value
    headers.cookie = `idToken=${idToken}`
    out = await fetch(STORE_URL, {
      method: 'POST',
      body: JSON.stringify({ query, variables }),
      headers
    }).then(r => r.json())
  } else {
    const s = STORE.get(STORE.idFromName(location))
    out = await s.fetch('https://store/graphql', {
      method: 'POST',
      body: JSON.stringify({ query, variables }),
      headers
    }).then(r => r.json())
  }

 let out

  if (process?.env?.NODE_ENV === 'development') {
    const cookieStore = cookies()
    const idToken = cookieStore.get('idToken')?.value
    headers.cookie = `idToken=${idToken}`
    out = await fetch(STORE_URL, {
      method: 'POST',
      body: JSON.stringify({ query, variables }),
      headers
    }).then(r => r.json())
  } else {
    const s = STORE.get(STORE.idFromName(location))
    out = await s.fetch('https://store/graphql', {
      method: 'POST',
      body: JSON.stringify({ query, variables }),
      headers
    }).then(r => r.json())
  }

 let out

  if (process?.env?.NODE_ENV === 'development') {
    const cookieStore = cookies()
    const idToken = cookieStore.get('idToken')?.value
    headers.cookie = `idToken=${idToken}`
    out = await fetch(STORE_URL, {
      method: 'POST',
      body: JSON.stringify({ query, variables }),
      headers
    }).then(r => r.json())
  } else {
    const s = STORE.get(STORE.idFromName(location))
    out = await s.fetch('https://store/graphql', {
      method: 'POST',
      body: JSON.stringify({ query, variables }),
      headers
    }).then(r => r.json())
  }

 let out

  if (process?.env?.NODE_ENV === 'development') {
    const cookieStore = cookies()
    const idToken = cookieStore.get('idToken')?.value
    headers.cookie = `idToken=${idToken}`
    out = await fetch(STORE_URL, {
      method: 'POST',
      body: JSON.stringify({ query, variables }),
      headers
    }).then(r => r.json())
  } else {
    const s = STORE.get(STORE.idFromName(location))
    out = await s.fetch('https://store/graphql', {
      method: 'POST',
      body: JSON.stringify({ query, variables }),
      headers
    }).then(r => r.json())
  }

R

rabbit1920•6/26/24, 2:43 PM

Hello.

R

rabbit1920•6/26/24, 2:43 PM

I'm getting Segmentation fault error while building project in cloudflare page

R

rabbit1920•6/26/24, 2:43 PM

I can't see any errors. above that error.

R

rabbit1920•6/26/24, 2:44 PM

Segmentation fault
10:17:05.158 ▲ error Command failed with exit code 139.
10:17:05.159 ▲ info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
10:17:05.174 ▲ Error: Command "yarn run build" exited with 139
10:17:05.250 ▲ error Command failed.
10:17:05.251 ▲ Exit code: 1
10:17:05.251 ▲ Command: vercel
10:17:05.251 ▲ Arguments: build
10:17:05.251 ▲ Directory: /opt/buildhome/repo
10:17:05.251 ▲ Output:
10:17:05.251 ▲ info Visit https://yarnpkg.com/en/docs/cli/exec for documentation about this command.
10:17:05.265
10:17:05.265

The Vercel build (

yarn exec vercel -- build

yarn exec vercel -- build

yarn exec vercel -- build

yarn exec vercel -- build) command failed. For more details see the Vercel logs above.
10:17:05.266

If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.

Rrabbit1920 Segmentation fault 10:17:05.158 ▲ error Command failed with exit code 139. 1...

J

James•6/27/24, 9:31 PM

Segmentation fault will likely be an issue with either how Next.js builds, or how the Vercel CLI processes it.

Rrabbit1920 Segmentation fault 10:17:05.158 ▲ error Command failed with exit code 139. 1...

N

Nob•6/27/24, 11:27 PM

@rabbit1920 is it crashing if you build in local ?

Nneoney gives me stuff like "ReferenceError: async__chunk_24831 is not defined" in prod ...

A

Alec | Kriebel LLC.•6/28/24, 2:05 AM

I also receiving this after upgrading to Next.js 14, from 13. It's causing my site to return 500 http, which means Google has stopped indexing and showing my site in search results.

Anyone have any solutions to this?

J

James•6/28/24, 6:11 AM

I'll upgrade one of my projects to next14 at some point next week and see if I can get the same problem to look into it

JJames I'll upgrade one of my projects to next14 at some point next week and see if I c...

A

Alec | Kriebel LLC.•6/28/24, 3:26 PM

Thank you! I've confirmed that downgrading to Next.js 13 without other code changes does indeed fix this issue. Let me know how if I can help out.

Original message was deleted