Do you get any errors? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

James

JJames Do you get any errors?

Befus

B

Befus•2/9/24, 6:50 PM

Not really, it just doesn't update

Befus

B

Befus•2/9/24, 6:50 PM

Would I have to change settings of cloudflare cache or does it work with the nextjs caching?

James

J

JamesOP•2/9/24, 7:01 PM

it uses the cache api in the worker

James

J

JamesOP•2/9/24, 7:02 PM

this is for a fetch request correct?

Befus

B

Befus•2/9/24, 7:02 PM

Not really, I am using server actions to get/put from my kv "directly"

James

J

JamesOP•2/9/24, 7:03 PM

I'm not sure I follow. What are you trying to revalidate with revalidatePath?

Befus

B

Befus•2/9/24, 7:04 PM

const Customers: FunctionComponent = async () => {
  const response = await getRequest("CUSTOMERS");

  const customers: Customer[] = await response.json();

  return <CustomerPage customers={customers} />;
};

export async function createCustomer(customer: z.infer<typeof customerSchema>) {
  try {
    // Send request to KV to create customer
    const id = uuidv4();

    // Cleanup data by removing empty objects or arrays or strings
    customer = removeEmptyData(customer);

    // add id to object
    customer.id = id;

    await putRequest("CUSTOMERS", "id:" + id, customer);

    // Return success message
    return {
      message: "Customer created",
      description: `"${customer.firstName} ${customer.name}" has been created successfully`,
      success: true,
      data: customer,
    };
  } catch (error) {
    return {
      message: "Error creating customer",
      description: `"${customer.firstName} ${customer.name}" could not be created`,
      success: false,
    };
  } finally {
    // Revalidate cache
    revalidatePath("/customers");
  }
}

const Customers: FunctionComponent = async () => {
  const response = await getRequest("CUSTOMERS");

  const customers: Customer[] = await response.json();

  return <CustomerPage customers={customers} />;
};

export async function createCustomer(customer: z.infer<typeof customerSchema>) {
  try {
    // Send request to KV to create customer
    const id = uuidv4();

    // Cleanup data by removing empty objects or arrays or strings
    customer = removeEmptyData(customer);

    // add id to object
    customer.id = id;

    await putRequest("CUSTOMERS", "id:" + id, customer);

    // Return success message
    return {
      message: "Customer created",
      description: `"${customer.firstName} ${customer.name}" has been created successfully`,
      success: true,
      data: customer,
    };
  } catch (error) {
    return {
      message: "Error creating customer",
      description: `"${customer.firstName} ${customer.name}" could not be created`,
      success: false,
    };
  } finally {
    // Revalidate cache
    revalidatePath("/customers");
  }
}

Befus

B

Befus•2/9/24, 7:04 PM

This may make it more clear, when creating or updating I would like it to "live" update for the user, I thought revalidatePath would do that

Befus

B

Befus•2/9/24, 7:05 PM

In the front end of the createCustomer you get redirected back to the customers page so I would assume the getRequests gets triggered again

James

J

JamesOP•2/9/24, 7:08 PM

I'm not sure I understand what is supposed to be cached that you're trying to revalidate here

Befus

B

Befus•2/9/24, 7:21 PM

I would think the customers that I am getting would get cached and then when I add one to the kv, it redirects again so the getRequest goes off.
Now that I am typing it, it seems that I am using it wrong or something

Befus

B

Befus•2/9/24, 7:22 PM

I was thinking that I could use the cache for live updates instead of having a useState

Befus

B

Befus•2/9/24, 7:24 PM

Do you have any suggestions since I feel like I am doing this wrong

Jeff

J

Jeff•2/10/24, 7:05 PM

Hello - I'm experiencing segfaults using next-on-pages, it seems to happen right when it starts the vercel part. Build ID: da4ccfcb-0266-4456-a60d-d43e94c95880da4ccfcb-0266-4456-a60d-d43e94c95880

Jeff

J

Jeff•2/10/24, 7:05 PM

I've tried both experimental.cpus=2experimental.cpus=2 and NODE_OPTIONS=--max-old-space-size=8192NODE_OPTIONS=--max-old-space-size=8192. Builds locally

James

J

JamesOP•2/10/24, 9:34 PM

Probably a memory leak in Next.js I would guess, have heard of several people running into that kind of situation before :/

Befus

BBefus Do you have any suggestions since I feel like I am doing this wrong

James

J

JamesOP•2/10/24, 9:35 PM

I mean, I'm still not sure I really understand what is supposed to be cached? revalidatePath is generally used to revalidate fetch cache entries afaik

Befus

B

Befus•2/10/24, 9:43 PM

I would think that when in this case I get my customers from the kv that would be cached? But when logging it I got this

Befus

B

Befus•2/10/24, 9:43 PM

James

JJames I mean, I'm still not sure I really understand what is supposed to be cached? re...

Befus

B

Befus•2/10/24, 9:44 PM

https://nextjs.org/docs/app/building-your-application/caching#react-cache-function

Building Your Application: Caching | Next.js

An overview of caching mechanisms in Next.js.

Befus

B

Befus•2/10/24, 9:45 PM

I was trying to do this with server actions, therefor don't really need the fetch but I guess I might need to

Befus

BBefus https://nextjs.org/docs/app/building-your-application/caching#react-cache-functi...

James

J

JamesOP•2/10/24, 10:15 PM

That is just to dedupe function calls essentially

James

J

JamesOP•2/10/24, 10:16 PM

I haven't read about revalidatePath applying to that so I'm not sure if it should or not tbh

James

JJames That is just to dedupe function calls essentially

Befus

B

Befus•2/10/24, 10:16 PM

Yea true

James

J

JamesOP•2/10/24, 10:16 PM

But I don't see how that would persist for you to be able to revalidate it anyway between requests

James

J

JamesOP•2/10/24, 10:17 PM

The only cache that persists between requests is the fetch cache

Befus

B

Befus•2/10/24, 10:17 PM

I think atm none of my requests gets cached, I believe thats the issue

Befus

B

Befus•2/10/24, 10:17 PM

Yea

Befus

B

Befus•2/10/24, 10:18 PM

I'm gonna try to use fetch and see if that works, don't really understand why they brought server actions if you need to use fetch for the cache

pthrbn

P

pthrbn•2/11/24, 6:02 AM

Can someone provide a working example of Nextjs 14 working with supabase? I've gotten auth mostly working but can't figure out basic queries

James

J

JamesOP•2/11/24, 12:53 PM

Never used supabase so I don't have an example, but are there any errors that you're running into?

Frixels

F

Frixels•2/11/24, 1:41 PM

Hello,

I got error on vercel/og while deploying to pages

⚡️ Completed npx vercel build.
15:03:21.826    ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
15:03:21.864    Finished

⚡️ Completed npx vercel build.
15:03:21.826    ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
15:03:21.864    Finished

Frixels

F

Frixels•2/11/24, 1:42 PM

⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/Users/usr/Documents/jsfun/nop/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/Users/usr/Documents/jsfun/nop/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'

⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/Users/usr/Documents/jsfun/nop/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/Users/usr/Documents/jsfun/nop/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'

Frixels

FFrixels Hello, I got error on vercel/og while deploying to pages `⚡️ Completed npx v...

Asher

A

Asher•2/11/24, 2:42 PM

I would try removing the .vercel and .next directories. That should fix it.

Asher

AAsher I would try removing the .vercel and .next directories. That should fix it.

Frixels

F

Frixels•2/11/24, 8:18 PM

Not working, also tried clear the cache still failed.

Asher

A

Asher•2/11/24, 8:19 PM

Remove node_modules and the lock file for your package manager and run the install command

Frixels

F

Frixels•2/11/24, 8:20 PM

Yeah did that couple time, I assume the lockfile was broken. After rebuild then I push back to git still failed to deploy.

Frixels

F

Frixels•2/11/24, 8:20 PM

removed the og function, worked fine

James

JJames Probably a memory leak in Next.js I would guess, have heard of several people ru...

Jeff

J

Jeff•2/12/24, 2:41 PM

Thanks. Any advice on how I can troubleshoot and or reduce memory usage in build step?

If not, are there guides anywhere on how to upload to pages from local after building? I tried uploading the .vercel folder but the generated cf pages url 404s, I probably made a mistake

Jeff

JJeff Thanks. Any advice on how I can troubleshoot and or reduce memory usage in build...

James

J

JamesOP•2/12/24, 9:23 PM

Afraid I don't. Regarding the other part though, you can use wrangler to deploy your application with npx wrangler pages deploy .vercel/output/staticnpx wrangler pages deploy .vercel/output/static

avl

Aavl Uncaught SyntaxError: Missing initializer in destructuring declaration

James

J

JamesOP•2/12/24, 9:24 PM

sounds like a potential issue with a library you use or something, or maybe a nextjs bug(?) or caching issue if you have caching in front of pages

beeman

B

beeman•2/12/24, 10:20 PM

Friends don't let friends use Next.

James

J

JamesOP•2/13/24, 6:20 AM

Ok

Simone Lusenti

SSimone Lusenti Hi! I just started testing next-on-pages, copy-pasting commands from the officia...

James

J

JamesOP•2/13/24, 7:55 PM

Sounds like you're taking an issue with Next.js' dev server? If so, that'd be something to raise with next.js I think

avl

Aavl what about this? Error 1102 Ray ID: XXX • 2024-02-13 09:40:00 UTC Worker exceede...

James

J

JamesOP•2/13/24, 7:56 PM

What are your routes doing?

⚡️ Completed npx vercel build.
15:03:21.826    ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
15:03:21.864    Finished

⚡️ Completed npx vercel build.
15:03:21.826    ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
15:03:21.864    Finished

⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/Users/usr/Documents/jsfun/nop/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/Users/usr/Documents/jsfun/nop/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'

⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/Users/usr/Documents/jsfun/nop/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/Users/usr/Documents/jsfun/nop/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'

const Customers: FunctionComponent = async () => {
  const response = await getRequest("CUSTOMERS");

  const customers: Customer[] = await response.json();

  return <CustomerPage customers={customers} />;
};

export async function createCustomer(customer: z.infer<typeof customerSchema>) {
  try {
    // Send request to KV to create customer
    const id = uuidv4();

    // Cleanup data by removing empty objects or arrays or strings
    customer = removeEmptyData(customer);

    // add id to object
    customer.id = id;

    await putRequest("CUSTOMERS", "id:" + id, customer);

    // Return success message
    return {
      message: "Customer created",
      description: `"${customer.firstName} ${customer.name}" has been created successfully`,
      success: true,
      data: customer,
    };
  } catch (error) {
    return {
      message: "Error creating customer",
      description: `"${customer.firstName} ${customer.name}" could not be created`,
      success: false,
    };
  } finally {
    // Revalidate cache
    revalidatePath("/customers");
  }
}

const Customers: FunctionComponent = async () => {
  const response = await getRequest("CUSTOMERS");

  const customers: Customer[] = await response.json();

  return <CustomerPage customers={customers} />;
};

export async function createCustomer(customer: z.infer<typeof customerSchema>) {
  try {
    // Send request to KV to create customer
    const id = uuidv4();

    // Cleanup data by removing empty objects or arrays or strings
    customer = removeEmptyData(customer);

    // add id to object
    customer.id = id;

    await putRequest("CUSTOMERS", "id:" + id, customer);

    // Return success message
    return {
      message: "Customer created",
      description: `"${customer.firstName} ${customer.name}" has been created successfully`,
      success: true,
      data: customer,
    };
  } catch (error) {
    return {
      message: "Error creating customer",
      description: `"${customer.firstName} ${customer.name}" could not be created`,
      success: false,
    };
  } finally {
    // Revalidate cache
    revalidatePath("/customers");
  }
}