it's something specific about the blog/[slug] page, so maybe you could take parts out of that page u

JJames it's something specific about the blog/[slug] page, so maybe you could take part...

D

dot•2/20/24, 7:13 PM

Could you help me by looking at the code ? I could provide you a sample of our code, the blog subfolder

JJames https://github.com/cloudflare/workerd/issues/1513

M

maitreya•2/20/24, 7:35 PM

I'm subscribed to that issue.

Is there any timelines on when the fix will be live?

JJames A minimal reproduction would be appreciated if possible

M

Morgan•2/20/24, 8:41 PM

Here's a minimal reproduction: https://github.com/cloudflare/next-on-pages/issues/672

GitHub

[🐛 Bug]: Unexpected error: ENOENT: no such file or directory · Issu...

next-on-pages environment related information No response Description Cloudflare build fails when using git integration on a minimal repository containing create-next-app and an additional file loc...

D

dot•2/21/24, 8:32 AM

When deleting the blog folder, the error move on to another folder, etc

D

dot•2/21/24, 8:33 AM

It's a never ending error

D

dot•2/21/24, 8:33 AM

is there anything specific to install for wasm to be generated

D

dot•2/21/24, 8:42 AM

Ok so I've managed to find the issue

D

dot•2/21/24, 8:43 AM

import { ImageResponse } from 'next/og'
import Image from 'next/image' 

// Route segment config
export const runtime = 'edge'
 
// Image metadata
export const size = {
  width: 32,
  height: 32,
}
export const contentType = 'image/png'
 
// Image generation
export default function Icon() {
  return new ImageResponse(
    (
      // ImageResponse JSX element
     <Image height={size.height} width={size.width} src="/favicons/apple-icon-180x180.png" alt="PurpleHosting - Icon" />

    ),
    // ImageResponse options
    {
      // For convenience, we can re-use the exported icons size metadata
      // config to also set the ImageResponse's width and height.
      ...size,
    }
  )
}

import { ImageResponse } from 'next/og'
import Image from 'next/image' 

// Route segment config
export const runtime = 'edge'
 
// Image metadata
export const size = {
  width: 32,
  height: 32,
}
export const contentType = 'image/png'
 
// Image generation
export default function Icon() {
  return new ImageResponse(
    (
      // ImageResponse JSX element
     <Image height={size.height} width={size.width} src="/favicons/apple-icon-180x180.png" alt="PurpleHosting - Icon" />

    ),
    // ImageResponse options
    {
      // For convenience, we can re-use the exported icons size metadata
      // config to also set the ImageResponse's width and height.
      ...size,
    }
  )
}

import { ImageResponse } from 'next/og'
import Image from 'next/image' 

// Route segment config
export const runtime = 'edge'
 
// Image metadata
export const size = {
  width: 32,
  height: 32,
}
export const contentType = 'image/png'
 
// Image generation
export default function Icon() {
  return new ImageResponse(
    (
      // ImageResponse JSX element
     <Image height={size.height} width={size.width} src="/favicons/apple-icon-180x180.png" alt="PurpleHosting - Icon" />

    ),
    // ImageResponse options
    {
      // For convenience, we can re-use the exported icons size metadata
      // config to also set the ImageResponse's width and height.
      ...size,
    }
  )
}

import { ImageResponse } from 'next/og'
import Image from 'next/image' 

// Route segment config
export const runtime = 'edge'
 
// Image metadata
export const size = {
  width: 32,
  height: 32,
}
export const contentType = 'image/png'
 
// Image generation
export default function Icon() {
  return new ImageResponse(
    (
      // ImageResponse JSX element
     <Image height={size.height} width={size.width} src="/favicons/apple-icon-180x180.png" alt="PurpleHosting - Icon" />

    ),
    // ImageResponse options
    {
      // For convenience, we can re-use the exported icons size metadata
      // config to also set the ImageResponse's width and height.
      ...size,
    }
  )
}

D

dot•2/21/24, 8:43 AM

this is what's causing the issue, deleted it

B

Befus•2/21/24, 3:20 PM

I managed to get Next-on-pages working with D1 and drizzle and it works in production but am currently getting this error local:
I just run npm run dev with setupDevPlatform as stated in the docs

Code:

export async function GET(request: NextRequest) {
  const db = drizzle(process.env.DB);
  console.log("DB", db)
  const customers = await db.select().from(users).all()

  return new Response(JSON.stringify(customers), {
    headers: { "Content-Type": "application/json" },
  });
}

export async function GET(request: NextRequest) {
  const db = drizzle(process.env.DB);
  console.log("DB", db)
  const customers = await db.select().from(users).all()

  return new Response(JSON.stringify(customers), {
    headers: { "Content-Type": "application/json" },
  });
}

export async function GET(request: NextRequest) {
  const db = drizzle(process.env.DB);
  console.log("DB", db)
  const customers = await db.select().from(users).all()

  return new Response(JSON.stringify(customers), {
    headers: { "Content-Type": "application/json" },
  });
}

export async function GET(request: NextRequest) {
  const db = drizzle(process.env.DB);
  console.log("DB", db)
  const customers = await db.select().from(users).all()

  return new Response(JSON.stringify(customers), {
    headers: { "Content-Type": "application/json" },
  });
}

C

conqr ᯅ•2/21/24, 9:31 PM

Is wrangler.toml ignored for next-on-pages

Cconqr ᯅ Is wrangler.toml ignored for next-on-pages

H

Hello, I’m Allie!•2/21/24, 9:32 PM

On deploy, yes

C

conqr ᯅ•2/21/24, 9:32 PM

I have

compatibility_flags = ["nodejs_compat"]

compatibility_flags = ["nodejs_compat"]

compatibility_flags = ["nodejs_compat"]

compatibility_flags = ["nodejs_compat"] in wrangler.toml but on publish, the deployed result says it must be enabled from dash

HHello, I’m Allie!On deploy, yes

C

conqr ᯅ•2/21/24, 9:32 PM

So all bindings and config must be done from dashboard?

Cconqr ᯅ So all bindings and config must be done from dashboard?

H

Hello, I’m Allie!•2/21/24, 9:34 PM

Yes

C

conqr ᯅ•2/21/24, 11:05 PM

I'm getting this error when trying to call

getRequestContext

getRequestContext

getRequestContext

getRequestContext from a next handler for local dev

C

conqr ᯅ•2/21/24, 11:06 PM

I have this in next.config.mjs:

import { setupDevPlatform } from "@cloudflare/next-on-pages/next-dev";

if (process.env.NODE_ENV === "development") {
  await setupDevPlatform({});
}

import { setupDevPlatform } from "@cloudflare/next-on-pages/next-dev";

if (process.env.NODE_ENV === "development") {
  await setupDevPlatform({});
}

import { setupDevPlatform } from "@cloudflare/next-on-pages/next-dev";

if (process.env.NODE_ENV === "development") {
  await setupDevPlatform({});
}

import { setupDevPlatform } from "@cloudflare/next-on-pages/next-dev";

if (process.env.NODE_ENV === "development") {
  await setupDevPlatform({});
}

C

conqr ᯅ•2/21/24, 11:06 PM

I'm on @cloudflare/next-on-pages version 1.9.0

C

conqr ᯅ•2/21/24, 11:12 PM

Do I not need to use getRequestContext?

C

conqr ᯅ•2/21/24, 11:13 PM

The example included with the S3 next on pages uses it, but on the Cloudflare Docs, it just uses process.env https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site

Cloudflare Docs

Full-stack deployment · Cloudflare Pages docs

Deploy a full-stack Next.js site (recommended).

Cconqr ᯅ I'm getting this error when trying to call `getRequestContext` from a next handl...

D

Dario•2/21/24, 11:35 PM

are you calling the

getRequestContext

getRequestContext

getRequestContext

getRequestContext utility in the edge runtime?

DDario are you calling the `getRequestContext` utility in the edge runtime?

C

conqr ᯅ•2/21/24, 11:36 PM

I switched to using

process.env

process.env

process.env

process.env and it worked actually

C

conqr ᯅ•2/21/24, 11:38 PM

And yeah, I'm calling from the edge runtime

D

Dario•2/21/24, 11:38 PM

could you provide a reproduction of it? if

process.env

process.env

process.env

process.env works

getRequestContext

getRequestContext

getRequestContext

getRequestContext should work as well

C

conqr ᯅ•2/21/24, 11:39 PM

I found the issue, I didn't add

export const runtime = "edge";

export const runtime = "edge";

export const runtime = "edge";

export const runtime = "edge";

C

conqr ᯅ•2/21/24, 11:39 PM

process.env

process.env

process.env

process.env worked without it somehow

Cconqr ᯅ I found the issue, I didn't add `export const runtime = "edge";`

D

Dario•2/21/24, 11:39 PM

ah!

Cconqr ᯅ `process.env` worked without it somehow

D

Dario•2/21/24, 11:40 PM

weird.... what were you trying to access?

DDario weird.... what were you trying to access?

C

conqr ᯅ•2/21/24, 11:40 PM

an env variable

D

Dario•2/21/24, 11:40 PM

could it be that in

process.env

process.env

process.env

process.env you had used the same variable name for something else?

C

conqr ᯅ•2/21/24, 11:41 PM

I think what happened is the nextjs dev server loaded

.env

.env

into

process.env

process.env

process.env

process.env

D

Dario•2/21/24, 11:41 PM

yeah, it does that

C

conqr ᯅ•2/21/24, 11:41 PM

I had it in

.env

.env

too

D

Dario•2/21/24, 11:42 PM

ok yeah that makes sense then

X

X•2/21/24, 11:43 PM

D

Dario•2/21/24, 11:49 PM

@conqr ᯅ I'll improve our error message to remind developers to use the edge runtime

, hopefully this can help avoid developers confusion/frustration: https://github.com/cloudflare/next-on-pages/issues/674

GitHub

[⚡ Feature]: Make local `getRequestContext` remind developers to us...

We've recently made the getRequestContext local error more helpful, reminding people to set up the dev platform: next-on-pages/packages/next-on-pages/src/api/getRequestContext.ts Lines 52 to 61...

C

conqr ᯅ•2/21/24, 11:50 PM

Still learning next, so I forget this quite often

D

Dario•2/21/24, 11:50 PM

yeah.... but it's not your fault, it's the problem of Next.js always defaulting to node.js

D

Dario•2/21/24, 11:51 PM

some versions back they did allow you to globally specify the edge runtime and have it applied to all your routes!

D

Dario•2/21/24, 11:51 PM

I so wish they didn't remove that

JJames Not sure what you mean by caching correctly? You typically don't cache pages whe...

C

chubbspeterson•2/22/24, 12:38 AM

You don't cache pages when you do SSR? That doesn't make sense to me.

Take for example a site with 10s of thousands of pages...it wouldn't be efficient to statically generate them all, so they would be generated server side and the response would be cached at the edge. This way the next request comes from cache vs generating it again

C

conqr ᯅ•2/22/24, 6:33 AM

What would this be caused by?

Screenshot_2024-02-21_at_10.32.47_PM.png

C

conqr ᯅ•2/22/24, 6:51 AM

Seems like NPM package htmlrewriter caused the issue :(

B

bigansh•2/22/24, 9:29 AM

the site is deployed, but i am getting 404 error. this is the url: https://testing.client-6ek.pages.dev/

B

bigansh•2/22/24, 9:30 AM

B

bigansh•2/22/24, 10:29 AM

ok, so i deleted the project and did it again, i got the worker limit error

B

bigansh•2/22/24, 10:30 AM

but when i ran this command

❯ yarn wrangler deploy .vercel/output/static/_worker.js/index.js --dry-run --compatibility-date 2024-02-22 --name test

❯ yarn wrangler deploy .vercel/output/static/_worker.js/index.js --dry-run --compatibility-date 2024-02-22 --name test

❯ yarn wrangler deploy .vercel/output/static/_worker.js/index.js --dry-run --compatibility-date 2024-02-22 --name test

❯ yarn wrangler deploy .vercel/output/static/_worker.js/index.js --dry-run --compatibility-date 2024-02-22 --name test

it showed me this size. not sure what the issue here is