Hard to see what is happening here when we don't see how the pages are generated in e.g. the next.js

V

veeque•8/15/24, 7:37 AM

i have an app where the user has access to a dashboard, makes some customisations that get pushed to a db, then if a user's customer goes to

myapp.com/the-users-name

myapp.com/the-users-name

myapp.com/the-users-name

myapp.com/the-users-name they will see a page that gets rendered based on the customisations applied. to do this in vercel i would use isr with

revalidatePath()

revalidatePath()

revalidatePath()

revalidatePath(), since cf doesn't support it, do i just have to put

export const runtime = 'edge'

export const runtime = 'edge'

export const runtime = 'edge'

export const runtime = 'edge' on the dynamic route and just have every request count towards the workers usage quota, correct?

J

James•8/15/24, 8:54 AM

yes

V

veeque•8/15/24, 9:00 AM

ight, thanks

F

Firu•8/16/24, 2:57 AM

Does anyone have recommendations for lightweight error logging SaaS products for next-on-pages? Adding Sentry doesn't seem to pass the Pages build

I

ItsWendellOP•8/16/24, 7:38 AM

@Firu I'm personally pushing logs and errors into Axiom, for front-end and back-end (https://axiom.co), it's not as feature-rich as Sentry but it does the job.

IItsWendell <@112215213553541120> I'm personally pushing logs and errors into Axiom, for fro...

F

Firu•8/16/24, 8:45 AM

I was looking at the same thing after my escapades in trying to get Sentry or Logpush to work. How's the integration experience? Could you please point me towards the docs you used?

F

Firu•8/16/24, 8:46 AM

also does it bloat for bundle size on deployment? Sentry adds 1.6Mb to all my frontend routes - which led to me going way past the upload size limit for a worker

FFiru also does it bloat for bundle size on deployment? Sentry adds 1.6Mb to all my fr...

H

Hard@Work•8/16/24, 8:50 AM

It's pretty easy. You can just lob a JSON object at

https://api.axiom.co/v1/datasets/$DATASET_NAME/ingest

https://api.axiom.co/v1/datasets/$DATASET_NAME/ingest

https://api.axiom.co/v1/datasets/$DATASET_NAME/ingest

https://api.axiom.co/v1/datasets/$DATASET_NAME/ingest with a Bearer token

H

Hard@Work•8/16/24, 8:50 AM

nvm, just reread the convo

H

Hard@Work•8/16/24, 8:51 AM

Yeah, just throw a JSON object like

{
  "error": "SomeString"
  "context1": "SomethingElse"
  // ...
}

{
  "error": "SomeString"
  "context1": "SomethingElse"
  // ...
}

{
  "error": "SomeString"
  "context1": "SomethingElse"
  // ...
}

{
  "error": "SomeString"
  "context1": "SomethingElse"
  // ...
}

HHard@Work It's pretty easy. You can just lob a JSON object at `https://api.axiom.co/v1/dat...

F

Firu•8/16/24, 9:42 AM

oh sweet, an HTTP endpoint

F

Firu•8/16/24, 9:42 AM

i'll have a look. thanks @Hard@Work & @ItsWendell !

HHard@Work It's pretty easy. You can just lob a JSON object at `https://api.axiom.co/v1/dat...

F

Firu•8/16/24, 10:09 AM

do you have any experience with their next-axiom library?

FFiru do you have any experience with their [next-axiom](https://github.com/axiomhq/ne...

H

Hard@Work•8/16/24, 11:49 AM

No, I do not(in fact, I don't use Next much anymore)

HHard@Work No, I do not(in fact, I don't use Next much anymore)

F

Firu•8/16/24, 12:41 PM

anymore

what happened?

F

Firu•8/16/24, 12:41 PM

also update on Axiom, works very well so far without bloating the bundle. i love the non-opinionated nature of it

FFiru > anymore what happened?

H

Hard@Work•8/16/24, 12:59 PM

No real issues with Next, I just haven't used it in a while. Last I used it for my blog, which is now on Astro

HHard@Work No real issues with Next, I just haven't used it in a while. Last I used it for ...

F

Firu•8/16/24, 1:02 PM

How's the Astro experience on Cloudflare Pages? anything particular pain points or is it smooth so far? it looks pretty promising

FFiru How's the Astro experience on Cloudflare Pages? anything particular pain points ...

I

Isaac McFadyen•8/16/24, 1:12 PM

Quite smooth from my experience + what I've seen around here. Depends on what you're doing of course, but overall it seems pretty good.

FFiru also update on Axiom, works very well so far without bloating the bundle. i love...

I

ItsWendellOP•8/16/24, 1:42 PM

Likewise, a small little tip, I've two different loggers, one for server components / ssr / middleware and one (using a hook) for client components.

The reason I do this is that I can add more context to the logs this way based on which context we are, here's rough examples:

Probably smarter ways to do this but this has worked pretty well!

message.txt3.26KB

IItsWendell Likewise, a small little tip, I've two different loggers, one for server compone...

F

Firu•8/16/24, 1:45 PM

this makes sense, definitely think it's a good idea to split the logs based on context

F

Firu•8/16/24, 1:45 PM

thanks for the advice!

D

D Trombett•8/16/24, 4:16 PM

First time using Pages with Next.js, I was wondering if I can retrieve data from D1 directly from a Server Component, so that I can display that data on the page without needing to make an API call to another worker

K

kiko•8/16/24, 5:48 PM

Is there a Cloudflare equivalent to Cloudinary's remote image fetch? And is there any good documentation on using it with Next's Image component?

Kkiko Is there a Cloudflare equivalent to Cloudinary's remote image fetch? And is ther...

S

Scai•8/18/24, 12:25 AM

https://developers.cloudflare.com/images/transform-images/integrate-with-frameworks/

Cloudflare Docs

Integrate with frameworks | Cloudflare Image Optimization docs

Image transformations can be used automatically with the Next.js <Image /> component.

S

Scai•8/18/24, 12:27 AM

Hey, I think this happened before for some people and I'm not the first one. I have a page with a custom header component which fetches a external service and I seted to revalidate cache in 3 mins, but the page is building as static page. The header component is used on every page and if I put the runtime edge in root layout all the pages aren't anymore static rendereded.

S

Scai•8/18/24, 12:28 AM

Example of function created:

src/lib/uptime.ts
export const areMonitorsDown = async () => {
  const response = await fetch(
    "your_awesome_monitoring_service_url",
    {
      method: "GET",
      headers: {
        "Content-Type": "application/json",
        Authorization: `Bearer ${process.env.API_KEY}`,
      },
      next: {
        // Cache the response for 3 minutes
        revalidate: 3 * 60,
      },
    }
  );

  if (response.status !== 200) {
    console.error("Failed to fetch monitors", response);
    return null;
  }

  const body = await response.json();
  const monitors = body.data;
  return monitors.some((monitor: any) => monitor.attributes.status === "down");
};

src/lib/uptime.ts
export const areMonitorsDown = async () => {
  const response = await fetch(
    "your_awesome_monitoring_service_url",
    {
      method: "GET",
      headers: {
        "Content-Type": "application/json",
        Authorization: `Bearer ${process.env.API_KEY}`,
      },
      next: {
        // Cache the response for 3 minutes
        revalidate: 3 * 60,
      },
    }
  );

  if (response.status !== 200) {
    console.error("Failed to fetch monitors", response);
    return null;
  }

  const body = await response.json();
  const monitors = body.data;
  return monitors.some((monitor: any) => monitor.attributes.status === "down");
};

src/lib/uptime.ts
export const areMonitorsDown = async () => {
  const response = await fetch(
    "your_awesome_monitoring_service_url",
    {
      method: "GET",
      headers: {
        "Content-Type": "application/json",
        Authorization: `Bearer ${process.env.API_KEY}`,
      },
      next: {
        // Cache the response for 3 minutes
        revalidate: 3 * 60,
      },
    }
  );

  if (response.status !== 200) {
    console.error("Failed to fetch monitors", response);
    return null;
  }

  const body = await response.json();
  const monitors = body.data;
  return monitors.some((monitor: any) => monitor.attributes.status === "down");
};

src/lib/uptime.ts
export const areMonitorsDown = async () => {
  const response = await fetch(
    "your_awesome_monitoring_service_url",
    {
      method: "GET",
      headers: {
        "Content-Type": "application/json",
        Authorization: `Bearer ${process.env.API_KEY}`,
      },
      next: {
        // Cache the response for 3 minutes
        revalidate: 3 * 60,
      },
    }
  );

  if (response.status !== 200) {
    console.error("Failed to fetch monitors", response);
    return null;
  }

  const body = await response.json();
  const monitors = body.data;
  return monitors.some((monitor: any) => monitor.attributes.status === "down");
};

S

Scai•8/18/24, 12:52 AM

How I could achieve that only that part of header is updated and rest remain static?

Wwindygod9986 Hey, I am trying to access D1 database binding in my server action using process...

S

Scai•8/18/24, 4:10 PM

Did you setup the cloudflare package on Next config?

S

Scai•8/18/24, 4:17 PM

The page where you use server actions, what render method it use?

S

Scai•8/18/24, 4:18 PM

That's on development env?

S

Scai•8/18/24, 4:18 PM

I would check all steps from here: https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/get-started/

S

Scai•8/18/24, 4:19 PM

Yeah, and that client component is used on a page after all

S

Scai•8/18/24, 4:20 PM

In my case I was using a server action in header and it wasn't executed because it was static rendered and not on edge runtime.

S

Scai•8/18/24, 4:20 PM

Funny thing to change all pages to edge runtime.

D

Dalist•8/18/24, 5:43 PM

guys I'm using Next.js and want to use cloudflare pages with Puppeteer, which I'm assuming would run on workers instead of lambda functions, do you know a newer tutorial for Next.js, this one seems old:
https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects

FFiru I was looking at the same thing after my escapades in trying to get Sentry or Lo...

F

fletcher3•8/19/24, 11:41 AM

Hi, I was trying to add observability to our pages project, but I was also encountering an unreasonable bloat up of the bundle size. Using vercel/otel package as alternative also does not work due to another open issue. I opened a new issue regarding this, as I would really like to understand what is going on
https://github.com/cloudflare/next-on-pages/issues/860

GitHub

[🐛 Bug]: Sentry bloats up bundle size when building with npx @cloud...

next-on-pages environment related information System: Platform: darwin CPU: arm64 Apple M3 Pro Memory: 18 GB Shell: /bin/zsh Package Manager Used: npm (10.5.0) Relevant Packages: @cloudflare/next-o...

Ffletcher3 Hi, I was trying to add observability to our pages project, but I was also encou...

F

Firu•8/19/24, 11:42 AM

If you're ok with using another platform for o11y, I recommend Axiom

F

Firu•8/19/24, 11:42 AM

they don't bloat the bundles

FFiru If you're ok with using another platform for o11y, I recommend Axiom

F

fletcher3•8/20/24, 11:30 AM

Thanks, looks great, will definitely give it a go

Ffletcher3 Thanks, looks great, will definitely give it a go

F

Firu•8/20/24, 12:03 PM

sure thing! lemme know if you find any pitfalls or pain points i might've missed

I

ItsWendellOP•8/20/24, 12:38 PM

Axiom actually also supports a lot of the OpenTelemetry standard, I also haven't got vercel/otel to work yet, if someone did, that would be awesome so I can send those into axiom too.

IItsWendell Hard to see what is happening here when we don't see how the pages are generated...

S

sean.h•8/20/24, 1:07 PM

Sure, been on other things the last few days.

job-logs.txt284.59KB

N

neoney•8/22/24, 5:09 PM

getRequestContext doesn't seem to have hyperdrive?

N

neoney•8/22/24, 5:09 PM

it smissing

N

neoney•8/22/24, 5:10 PM

and when it starts

Hard to see what is happening here when we don't see how the pages are generated in e.g. the next.js

Similar Threads

Similar Threads

Similar Threads