ah cool! 😄 By the way, given our `next-dev` hacks we can actually easily make it available during

DDario ah cool! 😄 By the way, given our `next-dev` hacks we can actually easily make ...

D

Deo Kumar•2/14/24, 12:39 PM

Yes, something is better than nothing

DDario I've already heard of this issue: https://github.com/cloudflare/next-on-pages/is...

D

Deo Kumar•2/14/24, 12:44 PM

I shall provide the minimal reproduction for this issue later.
Thank you

DDeo Kumar I shall provide the minimal reproduction for this issue later. Thank you 🙏

D

DarioOP•2/14/24, 12:48 PM

Awesome, thank you very much

DDeo Kumar Yes, something is better than nothing 😁

D

DarioOP•2/14/24, 3:39 PM

https://github.com/cloudflare/next-on-pages/pull/664

GitHub

make (no-op) `caches` available in dev mode by dario-piotrowicz · P...

blocked by #663

S

slagathor•2/14/24, 6:44 PM

Hey! I'm trying to return CSS in the <head> my NextJS app using the experimental-edge runtime so there isn't a flicker on load. This works fine when building statically, but it's not working when using SSR on experimental-edge . Has anyone else ran into this issue?

JJames The only cache that persists between requests is the fetch cache

B

Befus•2/14/24, 11:13 PM

I tried when using fetch and still no luck. When looking at some pull requests of next-on-pages previously revalidatePath/next cache and caching wasnt supported yet. Could you confirm that it is now?

J

James•2/14/24, 11:14 PM

Yes we implemented support for the fetch cache a long time ago. Please send code snippets of what you're doing

B

Befus•2/14/24, 11:15 PM

Yea i just found the pr, sorry for that. I will provide code snippets tomorrow

DDario https://github.com/cloudflare/next-on-pages/pull/664 🙂👍

D

Deo Kumar•2/15/24, 9:06 AM

Thanks

M

Mongy•2/15/24, 3:11 PM

Has anyone here successfully ran a next pages app with a D1 db locally?
I did follow this setup and configuration: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#use-bindings-in-your-nextjs-application
Unfortunately I am not having any luck getting this to run.

Cloudflare Docs

Full-stack deployment · Cloudflare Pages docs

Deploy a full-stack Next.js site.

C

chubbspeterson•2/16/24, 7:36 PM

Trying to determine if SSR pages are caching correctly... Should I be seeing

cf-cache-status

cf-cache-status

response headers? This is a Next 13 app using SSR

C

chubbspeterson•2/16/24, 7:36 PM

https://next-ring.pages.dev/entertainment/beyonce-blue-shading-dua-lipa-grammys

JJames Yep, current theory is that there's some sort of runtime bug that causes the Asy...

M

maitreya•2/17/24, 7:42 AM

hey! I'm getting this error when using Drizzle orm. Is this fixed? any workarounds for this?

Mmaitreya hey! I'm getting this error when using Drizzle orm. Is this fixed? any workaroun...

P

pthrbn•2/17/24, 6:04 PM

Same here. Completely blocked

O

Oren•2/18/24, 12:28 AM

middleware redirects like this

return NextResponse.redirect(new URL("/auth", request.url));

return NextResponse.redirect(new URL("/auth", request.url));

are changing the view but not the url in the url bar
I'm forced to use

router.push

router.push

instead of

router.refresh

router.refresh

on auth success e.g

G

Georgi Vatsov•2/18/24, 11:17 PM

Anyone experienced an issue with trying to set multiple set-cookie headers being merged into one? I am using Auth.js and it fails, because of the session-token cookie and the code_verifier cookie are put both in one header.

G

Georgi Vatsov•2/18/24, 11:54 PM

Just tried on Vercel. This works properly there. Is there any workaround for this in Cloudflare or should I move?

GGeorgi Vatsov Anyone experienced an issue with trying to set multiple set-cookie headers being...

I

Isaac McFadyen•2/19/24, 1:49 AM

Set-cookie headers are allowed to be merged as long as they're joined with a comma... is that what you're seeing? https://stackoverflow.com/a/2880070

IIsaac McFadyen Set-cookie headers are allowed to be merged as long as they're joined with a com...

G

Georgi Vatsov•2/19/24, 7:20 AM

Yes, this is what I am seeing. But it does not work as expected - the cookie is never actually set.

GGeorgi Vatsov Anyone experienced an issue with trying to set multiple set-cookie headers being...

D

DarioOP•2/19/24, 6:54 PM

Hey @Georgi Vatsov, I think we had similar issues in the past, could you try using the latest version of next-on-pages? and if it doesn't work create a new issue (https://github.com/cloudflare/next-on-pages/issues/new?assignees=&labels=bug&projects=&template=bug-report.yml&title=%5B%F0%9F%90%9B+Bug%5D%3A+) with a minimal reproduction?

D

DarioOP•2/19/24, 6:57 PM

yeah.... I do feel like that should work!

https://github.com/cloudflare/next-on-pages/blob/3846730c4a0d12cda128d691160968d0a131a6f1/packages/next-on-pages/tests/templates/utils/http.test.ts#L46-L54

GitHub

next-on-pages/packages/next-on-pages/tests/templates/utils/http.tes...

CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages

Cchubbspeterson Trying to determine if SSR pages are caching correctly... Should I be seeing `cf...

J

James•2/19/24, 9:37 PM

Not sure what you mean by caching correctly? You typically don't cache pages when you do SSR

Mmaitreya hey! I'm getting this error when using Drizzle orm. Is this fixed? any workaroun...

J

James•2/19/24, 9:38 PM

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

OOren middleware redirects like this `return NextResponse.redirect(new URL("/auth", re...

J

James•2/19/24, 9:38 PM

Please open an issue if this is a bug

B

bun•2/19/24, 10:39 PM

in examples why do you guys have

// file: env.d.ts

interface CloudflareEnv {
    KV: KVNamespace;
}

// file: env.d.ts

interface CloudflareEnv {
    KV: KVNamespace;
}

// file: env.d.ts

interface CloudflareEnv {
    KV: KVNamespace;
}

// file: env.d.ts

interface CloudflareEnv {
    KV: KVNamespace;
}

if this is the correct version:

import { KVNamespace } from "@cloudflare/workers-types";

declare global {
  interface CloudflareEnv {
    KV: KVNamespace;
  }
}

import { KVNamespace } from "@cloudflare/workers-types";

declare global {
  interface CloudflareEnv {
    KV: KVNamespace;
  }
}

import { KVNamespace } from "@cloudflare/workers-types";

declare global {
  interface CloudflareEnv {
    KV: KVNamespace;
  }
}

import { KVNamespace } from "@cloudflare/workers-types";

declare global {
  interface CloudflareEnv {
    KV: KVNamespace;
  }
}

D

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

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

D

dot•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'

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.

D

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

Did you managed to fix your issue ?

Ddot Did you managed to fix your issue ?

M

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

D

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

M

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

M

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

Looks like the same error though.

D

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

J

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

D

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

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

J

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

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

ah cool! 😄 By the way, given our `next-dev` hacks we can actually easily make it available during

Similar Threads

Similar Threads

Similar Threads