I mean, I'm still not sure I really understand what is supposed to be cached? revalidatePath is gene

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

B

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

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

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.

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

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

J

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

That is just to dedupe function calls essentially

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

JJames That is just to dedupe function calls essentially

B

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

Yea true

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

J

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

The only cache that persists between requests is the fetch cache

B

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

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

B

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

Yea

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

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

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?

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

⚡️ 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

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'

⚡️ 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'

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

A

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

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

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

F

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

Not working, also tried clear the cache still failed.

A

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

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

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.

F

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

removed the og function, worked fine

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

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

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

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/static

npx wrangler pages deploy .vercel/output/static

npx wrangler pages deploy .vercel/output/static

npx wrangler pages deploy .vercel/output/static

Aavl Uncaught SyntaxError: Missing initializer in destructuring declaration

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

B

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

Friends don't let friends use Next.

J

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

Ok

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

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

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

J

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

What are your routes doing?

D

Deo Kumar•2/14/24, 8:17 AM

Tysm for the

getRequestContext

getRequestContext

getRequestContext

getRequestContext utility.

DDeo Kumar Tysm for the `getRequestContext` utility.

D

Deo Kumar•2/14/24, 11:22 AM

Is

caches

caches

caches

caches field (Cache API) accessible?

D

Deo Kumar•2/14/24, 11:42 AM

I am getting this build error when i try to import wasm

DDeo Kumar Is `caches` field (Cache API) accessible?

D

Dario•2/14/24, 12:28 PM

no it is not...

I guess we could support that...

although they, in production are just available from the global scope (and in dev you could check if

caches

caches

caches

caches is or not on the global scope?)

D

Dario•2/14/24, 12:30 PM

PS: we currently in the

getPlatformProxy

getPlatformProxy

getPlatformProxy

getPlatformProxy utility (used by next-on-pages under the hood) don't have a local dev support for

caches

caches

caches

caches: https://github.com/cloudflare/workers-sdk/issues/4879
(we just provide a no-op implementation)

DDeo Kumar I am getting this build error when i try to import wasm

D

Dario•2/14/24, 12:32 PM

I've already heard of this issue: https://github.com/cloudflare/next-on-pages/issues/39#issuecomment-1939591927
I imagine it's a bug in the next-on-pages build process, I'll have to look into it soon... would you happen to have a minimal reproduction?

DDario no it is not... 🤔 I guess we could support that... 🤔 although they, in pro...

D

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

Yep, I am currently doing that. Btw

getRequestContext

getRequestContext

getRequestContext

getRequestContext made things easier

DDeo Kumar Yep, I am currently doing that. Btw `getRequestContext` made things easier 🤭

D

Dario•2/14/24, 12:36 PM

ah cool!

By the way, given our

next-dev

next-dev

next-dev

next-dev hacks we can actually easily make it available during dev too... I can easily open a PR for that, but again the no-op implementation provided by

getPlatformProxy

getPlatformProxy

getPlatformProxy

getPlatformProxy is currently the best I can offer

would that be convenient for you? (I guess it'd save you the trouble to check if

caches

caches

caches

caches is or not on the global scope)

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

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

Awesome, thank you very much

DDeo Kumar Yes, something is better than nothing 😁

D

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

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

I mean, I'm still not sure I really understand what is supposed to be cached? revalidatePath is gene

Similar Threads

Similar Threads

Similar Threads