Hi, I'm getting an issue deploying to CF Pages: ``` 19:01:36.442 ▲ Build Completed in .vercel/

Hi,

I'm getting an issue deploying to CF Pages:

19:01:36.442    ▲  Build Completed in .vercel/output [57s]
19:01:36.553    ⚡️ Completed `npx vercel build`.
19:01:39.216    ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
19:01:39.272    Finished
19:01:39.273    Found _worker.js in output directory. Uploading.
19:01:40.514    Attaching additional modules:
19:01:40.515    - __next-on-pages-dist__/manifest/27d10e462fba646daaa29468a0656e12.js (esm)
19:01:40.515    - __next-on-pages-dist__/manifest/__RSC_SERVER_MANIFEST.js (esm)
19:01:40.515    - __next-on-pages-dist__/webpack/137.js (esm)
19:01:40.515    - __next-on-pages-dist__/webpack/1796.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/44bff480f105853cb03b9b061f5738d6.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/5303.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/6595.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/8775.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/8f135fd1cad616b24af4b973584a7795.js (esm)
19:01:40.677    ✘ [ERROR] 1 error(s) and 0 warning(s) when compiling Worker.
19:01:40.678    
19:01:40.678    
19:01:40.682    
19:01:40.683    ✘ [ERROR] Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.683    
19:01:40.683    
19:01:40.685    ✘ [ERROR] Build failed with 1 error:
19:01:40.685    
19:01:40.685      error: Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.685    
19:01:40.685    
19:01:40.698    Failed building Pages Functions.
19:01:41.641    Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

19:01:36.442    ▲  Build Completed in .vercel/output [57s]
19:01:36.553    ⚡️ Completed `npx vercel build`.
19:01:39.216    ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
19:01:39.272    Finished
19:01:39.273    Found _worker.js in output directory. Uploading.
19:01:40.514    Attaching additional modules:
19:01:40.515    - __next-on-pages-dist__/manifest/27d10e462fba646daaa29468a0656e12.js (esm)
19:01:40.515    - __next-on-pages-dist__/manifest/__RSC_SERVER_MANIFEST.js (esm)
19:01:40.515    - __next-on-pages-dist__/webpack/137.js (esm)
19:01:40.515    - __next-on-pages-dist__/webpack/1796.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/44bff480f105853cb03b9b061f5738d6.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/5303.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/6595.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/8775.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/8f135fd1cad616b24af4b973584a7795.js (esm)
19:01:40.677    ✘ [ERROR] 1 error(s) and 0 warning(s) when compiling Worker.
19:01:40.678    
19:01:40.678    
19:01:40.682    
19:01:40.683    ✘ [ERROR] Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.683    
19:01:40.683    
19:01:40.685    ✘ [ERROR] Build failed with 1 error:
19:01:40.685    
19:01:40.685      error: Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.685    
19:01:40.685    
19:01:40.698    Failed building Pages Functions.
19:01:41.641    Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

19:01:36.442    ▲  Build Completed in .vercel/output [57s]
19:01:36.553    ⚡️ Completed `npx vercel build`.
19:01:39.216    ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
19:01:39.272    Finished
19:01:39.273    Found _worker.js in output directory. Uploading.
19:01:40.514    Attaching additional modules:
19:01:40.515    - __next-on-pages-dist__/manifest/27d10e462fba646daaa29468a0656e12.js (esm)
19:01:40.515    - __next-on-pages-dist__/manifest/__RSC_SERVER_MANIFEST.js (esm)
19:01:40.515    - __next-on-pages-dist__/webpack/137.js (esm)
19:01:40.515    - __next-on-pages-dist__/webpack/1796.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/44bff480f105853cb03b9b061f5738d6.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/5303.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/6595.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/8775.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/8f135fd1cad616b24af4b973584a7795.js (esm)
19:01:40.677    ✘ [ERROR] 1 error(s) and 0 warning(s) when compiling Worker.
19:01:40.678    
19:01:40.678    
19:01:40.682    
19:01:40.683    ✘ [ERROR] Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.683    
19:01:40.683    
19:01:40.685    ✘ [ERROR] Build failed with 1 error:
19:01:40.685    
19:01:40.685      error: Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.685    
19:01:40.685    
19:01:40.698    Failed building Pages Functions.
19:01:41.641    Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

19:01:36.442    ▲  Build Completed in .vercel/output [57s]
19:01:36.553    ⚡️ Completed `npx vercel build`.
19:01:39.216    ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
19:01:39.272    Finished
19:01:39.273    Found _worker.js in output directory. Uploading.
19:01:40.514    Attaching additional modules:
19:01:40.515    - __next-on-pages-dist__/manifest/27d10e462fba646daaa29468a0656e12.js (esm)
19:01:40.515    - __next-on-pages-dist__/manifest/__RSC_SERVER_MANIFEST.js (esm)
19:01:40.515    - __next-on-pages-dist__/webpack/137.js (esm)
19:01:40.515    - __next-on-pages-dist__/webpack/1796.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/44bff480f105853cb03b9b061f5738d6.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/5303.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/6595.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/8775.js (esm)
19:01:40.516    - __next-on-pages-dist__/webpack/8f135fd1cad616b24af4b973584a7795.js (esm)
19:01:40.677    ✘ [ERROR] 1 error(s) and 0 warning(s) when compiling Worker.
19:01:40.678    
19:01:40.678    
19:01:40.682    
19:01:40.683    ✘ [ERROR] Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.683    
19:01:40.683    
19:01:40.685    ✘ [ERROR] Build failed with 1 error:
19:01:40.685    
19:01:40.685      error: Could not resolve "/opt/buildhome/repo/.vercel/output/static/_worker.js/index.js"
19:01:40.685    
19:01:40.685    
19:01:40.698    Failed building Pages Functions.
19:01:41.641    Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

dotOP•2/20/24, 6:05 PM

Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'

Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'

is the culprit but I don't know anything about what could cause it

MMorgan I'll see what I can do.

dotOP•2/20/24, 6:08 PM

Did you managed to fix your issue ?

Ddot Did you managed to fix your issue ?

Morgan•2/20/24, 6:13 PM

I removed the file that caused the issue and moved onto another problem, will come back to it though at some point.

MMorgan I removed the file that caused the issue and moved onto another problem, will co...

dotOP•2/20/24, 6:14 PM

Ok, I might aswell consider removing the blog but it's a main feature. Thank you for your feedback on this

Ddot Ok, I might aswell consider removing the blog but it's a main feature. Thank you...

Morgan•2/20/24, 6:15 PM

It wasn’t anything to do with a blog that caused the issue for me. It was a file that generates custom open graph images.

Ddot Ok, I might aswell consider removing the blog but it's a main feature. Thank you...

Morgan•2/20/24, 6:18 PM

Looks like the same error though.

dotOP•2/20/24, 6:50 PM

I've been able to replicate on my local setup, in the .vercel/output/functions/blog/[slug].func, there is no wasm folder, only these two files:
index.js index.js.map

Ddot Hi, I'm getting an issue deploying to CF Pages: ``` 19:01:36.442 ▲ Build C...

James•2/20/24, 7:00 PM

Please can you open an issue on the next-on-pages repo

JJames Please can you open an issue on the next-on-pages repo

dotOP•2/20/24, 7:04 PM

Yes but what about reproduction ? Can't provide a public access to my repo

James•2/20/24, 7:06 PM

it's something specific about the blog/[slug] page, so maybe you could take parts out of that page until you can reproduce it? possible it might be related to og images or something like that

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

dotOP•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

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

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...

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

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

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

It's a never ending error

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

is there anything specific to install for wasm to be generated

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

Ok so I've managed to find the issue

dotOP•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,
    }
  )
}

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

this is what's causing the issue, deleted it

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" },
  });
}

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

Is wrangler.toml ignored for next-on-pages

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

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

On deploy, yes

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

I have 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

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?

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

Yes

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

I'm getting this error when trying to call getRequestContextgetRequestContext from a next handler for local dev

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({});
}

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

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

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

Do I not need to use getRequestContext?

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...

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

are you calling the getRequestContextgetRequestContext utility in the edge runtime?

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

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

I switched to using process.envprocess.env and it worked actually

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

And yeah, I'm calling from the edge runtime

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

could you provide a reproduction of it? if process.envprocess.env works getRequestContextgetRequestContext should work as well

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

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

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

process.envprocess.env worked without it somehow

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

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

ah!

Cconqr ᯅ `process.env` worked without it somehow

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

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

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

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

an env variable

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

could it be that in process.envprocess.env you had used the same variable name for something else?

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

I think what happened is the nextjs dev server loaded .env.env into process.envprocess.env

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

yeah, it does that

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

I had it in .env.env too

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

ok yeah that makes sense then

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

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...

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

Still learning next, so I forget this quite often

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

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!

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

I so wish they didn't remove that

Hi, I'm getting an issue deploying to CF Pages: ``` 19:01:36.442 ▲ Build Completed in .vercel/

Similar Threads