I keep having this problem, when I update next-on-pages, my project stops working with a "XMLHttpReq

A

AAOP•10/2/24, 10:33 PM

I think i've mentioned it previously

A

AAOP•10/2/24, 10:40 PM

yea soon as i force 1.9.0 everything works ok

AAA any differences between 1.9.0 and 1.13.2 that would give me an "ReferenceError: ...

A

AAOP•10/3/24, 12:28 AM

yea, i knew i'd asked about it previously

J

James•10/3/24, 7:09 AM

That doesnt sound related to next-on-pages

B

bun•10/3/24, 11:21 AM

anyone had success integrating sentry.io on next-on-pages ? or is it not working? @Baran

AAA I keep having this problem, when I update next-on-pages, my project stops workin...

B

bun•10/3/24, 12:18 PM

seems like you are using axios on edge runtime

B

bun•10/3/24, 12:19 PM

maybe not use axios ? and use

requestly

requestly

requestly

requestly or some modern fetch library

JJames That doesnt sound related to next-on-pages

A

AAOP•10/3/24, 12:53 PM

I agree, which is why i'm confused. but the only thing I'm changing is the version of next-on-pages

A

AAOP•10/3/24, 12:53 PM

it makes me wonder if there is a dependency interaction that i'm not aware of

A

AAOP•10/3/24, 1:01 PM

the actual code change that made this work.. Tho the package.json change is massive

A

AAOP•10/3/24, 1:02 PM

removing this line, or changing the version starts producing the XMLHttpRequest

A

AAOP•10/3/24, 1:06 PM

yea. line change with that add on is +10354 -3237

AAA the actual code change that made this work.. Tho the package.json change is mas...

B

bun•10/3/24, 1:13 PM

are you using axios or not?

Bbun are you using axios or not?

A

AAOP•10/3/24, 1:14 PM

not directly, and i dont see it in any sub dependencies

A

AAOP•10/3/24, 1:15 PM

most everything is through a graphql library that could use axios, but has an override to use fetch

A

AAOP•10/3/24, 1:16 PM

axios does not appear in the package.lock

B

bun•10/3/24, 1:17 PM

what about cross-fetch ?

A

AAOP•10/3/24, 1:17 PM

indeed it does

B

bun•10/3/24, 1:18 PM

yeah that could be the cause, is there a way you can initiate a graphql client using your own fetch?

B

bun•10/3/24, 1:18 PM

it should have options

A

AAOP•10/3/24, 1:18 PM

yea you can override the fetch in the graphql client. if i dont do that it doesnt work on any version of next-on-pages

A

AAOP•10/3/24, 1:19 PM

required by node_modules/fbjs "node_modules/graphql-request":

A

AAOP•10/3/24, 1:24 PM

not familiar with fbjs, hmm

A

AAOP•10/3/24, 1:30 PM

not sure this explains why changing the next-on-pages version breaks this either

J

James•10/3/24, 1:55 PM

maybe it's updating other dependencies that aren't locked to specific patches too

Bbun anyone had success integrating sentry.io on next-on-pages ? or is it not working...

B

Baran•10/3/24, 3:42 PM

There is a fix coming to next-on-pages, so sentry will be implemented soon. I dont know when the next release date is

JJames maybe it's updating other dependencies that aren't locked to specific patches to...

A

AAOP•10/3/24, 4:25 PM

yea i'm wondering about that. its weird because if i changee this to the 1.10 or later it breaks, and then back it works.. just need to trace every dep i guess

BBaran There is a fix coming to next-on-pages, so sentry will be implemented soon. I do...

B

bun•10/3/24, 4:59 PM

Nice

B

bun•10/3/24, 4:59 PM

The only jssue with sentry and nextjs is the bundle size? Or is there something else @Baran

M

mr nooli•10/3/24, 5:00 PM

If bundle size is the issue, I think take a look at posthog - it's quite nice pricing wise and I think offers a somewhat similar service

A

AAOP•10/3/24, 8:29 PM

i wonder if there is a way to tell it to ignore the cross-fetch library.. it may be stealing the 'fetch' word, and not doing a good job on cloudflare

A

AAOP•10/3/24, 8:30 PM

just tried the 4.0 version of that lib which claims cf support, with no go

Mmr nooli If bundle size is the issue, I think take a look at posthog - it's quite nice pr...

B

bun•10/4/24, 1:43 AM

does it work on next-on-pages?

B

bun•10/4/24, 2:56 PM

@mr nooli

A

AAOP•10/4/24, 4:40 PM

Huh, if cross-fetch is an included package in my project, 'fetch' gets overwritten globally somehow if I'm using a specific combination of packages.. regardless if I import cross-fetch in my specific file.

A

AAOP•10/4/24, 4:40 PM

feels like a build problem, tho, is there a reference somewhere to the original fetch i can use?

A

AAOP•10/4/24, 5:00 PM

tho i wonder if i can do some next.config.js magic and tell it to use a local file for cross-fetch package

A

AAOP•10/4/24, 5:37 PM

heh, asked chatgpt.. https://chatgpt.com/share/6700278e-bc4c-8000-bd35-8d53b995c5a8

ChatGPT

A conversational AI system that listens, learns, and challenges

A

AAOP•10/4/24, 5:39 PM

it went a little sideways

L

lucasp•10/4/24, 8:04 PM

hello im getting this error, someone knows whats happend?

import { auth } from '@/auth'
import { getUser } from '@/client/services/user.service'
import Home from '@/components/pages/Home'
import { redirect } from 'next/navigation'

export const runtime = 'edge'

export default async function Main() {
  const session = await auth()

  const user = await getUser(session?.user?.localId ?? '')

  if (!user?.cargo_giver) redirect('/profile')

  return <Home />
}

import { auth } from '@/auth'
import { getUser } from '@/client/services/user.service'
import Home from '@/components/pages/Home'
import { redirect } from 'next/navigation'

export const runtime = 'edge'

export default async function Main() {
  const session = await auth()

  const user = await getUser(session?.user?.localId ?? '')

  if (!user?.cargo_giver) redirect('/profile')

  return <Home />
}

import { auth } from '@/auth'
import { getUser } from '@/client/services/user.service'
import Home from '@/components/pages/Home'
import { redirect } from 'next/navigation'

export const runtime = 'edge'

export default async function Main() {
  const session = await auth()

  const user = await getUser(session?.user?.localId ?? '')

  if (!user?.cargo_giver) redirect('/profile')

  return <Home />
}

import { auth } from '@/auth'
import { getUser } from '@/client/services/user.service'
import Home from '@/components/pages/Home'
import { redirect } from 'next/navigation'

export const runtime = 'edge'

export default async function Main() {
  const session = await auth()

  const user = await getUser(session?.user?.localId ?? '')

  if (!user?.cargo_giver) redirect('/profile')

  return <Home />
}

server side exception and when check logs

"logs": [
{
"message": [
"Error: The 'cache' field on 'RequestInitializerDict' is not implemented."
],

S

Spajk•10/4/24, 10:25 PM

This might be more of an nextjs issue then next-on-pages, but I randomly started getting this error:

S

Spajk•10/4/24, 10:25 PM

⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️ 
⚡️     The following routes were not configured to run with the Edge Runtime:
⚡️       - /_not-found

⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️ 
⚡️     The following routes were not configured to run with the Edge Runtime:
⚡️       - /_not-found

⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️ 
⚡️     The following routes were not configured to run with the Edge Runtime:
⚡️       - /_not-found

⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️ 
⚡️     The following routes were not configured to run with the Edge Runtime:
⚡️       - /_not-found

S

Spajk•10/4/24, 10:26 PM

The thing is, I don't have a not-found page

S

Spajk•10/4/24, 10:26 PM

I can see that previously in the build log it appeared as this

S

Spajk•10/4/24, 10:26 PM

Route (app)                                   Size     First Load JS
▲  ┌ ƒ /                                         8.18 kB        95.3 kB
▲  ├ ○ /_not-found                               873 B            88 kB

Route (app)                                   Size     First Load JS
▲  ┌ ƒ /                                         8.18 kB        95.3 kB
▲  ├ ○ /_not-found                               873 B            88 kB

Route (app)                                   Size     First Load JS
▲  ┌ ƒ /                                         8.18 kB        95.3 kB
▲  ├ ○ /_not-found                               873 B            88 kB

Route (app)                                   Size     First Load JS
▲  ┌ ƒ /                                         8.18 kB        95.3 kB
▲  ├ ○ /_not-found                               873 B            88 kB

S

Spajk•10/4/24, 10:27 PM

and that produced successful builds

S

Spajk•10/4/24, 10:27 PM

but now it's

S

Spajk•10/4/24, 10:27 PM

▲  Route (app)                                   Size     First Load JS
▲  ┌ ƒ /                                         3.64 kB        90.8 kB
▲  ├ ƒ /_not-found                               873 B            88 kB

▲  Route (app)                                   Size     First Load JS
▲  ┌ ƒ /                                         3.64 kB        90.8 kB
▲  ├ ƒ /_not-found                               873 B            88 kB

▲  Route (app)                                   Size     First Load JS
▲  ┌ ƒ /                                         3.64 kB        90.8 kB
▲  ├ ƒ /_not-found                               873 B            88 kB

▲  Route (app)                                   Size     First Load JS
▲  ┌ ƒ /                                         3.64 kB        90.8 kB
▲  ├ ƒ /_not-found                               873 B            88 kB

E

essequiel•10/4/24, 11:15 PM

hi everyone

E

essequiel•10/4/24, 11:16 PM

is there someone that can help me creating a dynamic page? when i create a folder and add a [id].tsx file inside, i can't make it work

I keep having this problem, when I update next-on-pages, my project stops working with a "XMLHttpReq

Similar Threads

Similar Threads

Similar Threads