[next.js] Doesn't work on Cloudflare Pages

[chrisbaume]

Steps:

1. Set up next.js template on Cloudflare Pages using this guide
2. npm install @logtail/next
3. In next.config.mjs, add export default withLogtail(nextConfig)
4. In middleware.ts add export default withLogtail(middleware)
5. Create the following page.tsx

import { log } from "@logtail/next";
export const runtime = "edge";
export default async function Page() {
  log.info('Next.js page log test')
  return <p>Done</p>
}

5. Create a .env.local with LOGTAIL_SOURCE_TOKEN and LOGTAIL_URL, then test locally using npm run dev.
6. Deploy to Cloudflare with env vars LOGTAIL_SOURCE_TOKEN and LOGTAIL_URL and test.

Results

When running locally, the logs appear as expected. When running on Cloudfare Pages, no logs appear.

[curusarn]

Hi @chrisbaume!

Thank you for raising this & including reproduction steps.
I'm passing it on to the team to take a look.
I'll get back to you here once we have any updates.

Thanks again for reaching out.

[chrisbaume]

We decided to migrate to OpenNext so that we can deploy to Workers, rather than Pages. This means we are now using logpush to ingest logs into BetterStack, which is a neater solution overall. I'm not sure what Cloudflare's long-term plans are, but they say:

We plan to bridge the gaps between Workers and Pages and provide ways to migrate your Pages projects to Workers.

which suggests that they may be deprecating Pages in the future.