Are you using a wrangler.toml file? You get undefined because it cant find the key anymore
Are you using a wrangler.toml file? You get undefined because it cant find the key anymore
MIn nextJs project we don't use wrangler.toml file because the configurations are in next.config.js
MBut when I get values from the terminal it works as expected.
MI already defined the KV in next.conf.js
Mwhy should I have a wrangler.toml file then ?
BWhy are you putting it in the next config? In the kv documentation it uses a wrangler.toml I believe
BIt makes it so youre values are also stored locally otherwise your code would only work in production
HNote that this only applies when using
wrangler pages devnext dev
BIf you use cf bindings proxy it fixes that aswell I believe, atleast thats how I do it
HYeah, that. Though, that doesn't require a
wrangler.tomlYou can pass bindings via the command line
BAh didnt know
Sstrangely I cannot get the ErrorBoundary to work at all, I tried that library and Sentry's one too
JBizarre
MHey,
MWhen I deploy my KV worker it doesn't read from the storage and give me null as response
MIs there any missed configuration ?
MHow to solve that ?
D
H
Rhello everyone, I want to ask about ftp configuration always on, where is should be I ask on? thank you!
JTry the general help channel perhaps
MI found this:
Is it compatible with pnpm?
Is it compatible with pnpm?
MAlso, this:
JThat error looks like it might be the culprit
JPlease can you open an issue on our GitHub repo with that error
MWill do
JA minimal reproduction would be appreciated if possible
MI'll see what I can do.
ADoes server actions works for anyone here? I am using Next 14.1.0 and all the server actions XHR requests are failing!
SI finally got error reporting with Sentry working well with next-on-pages
I started from scratch and used the Loader Script instead of their "automatic" setup
this works for some errors but not the ones caught by the built-in NextJS error boundary in production
so, I used
I started from scratch and used the Loader Script instead of their "automatic" setup
this works for some errors but not the ones caught by the built-in NextJS error boundary in production
so, I used
react-error-boundary to wrap my app like this, and now it catches everything and allowed us to customize the error page:JNice!
JServer actions should work. Please can you open a GitHub issue with a reproduction if they're not working for you?
MOn the surface it looks related to a route that generates an OG image.
MI have managed to get a Next.js 14 site working after changing all routes to "edge", but I'm getting errors on dynamic routes, how do I go about surfacing them?
Usually, with Vercel, I could add a console.log() and view the server logs to debug, how do I go about doing that with Cloudflare?
I've looked at realtime logs, but they only seem to contain headers.
Usually, with Vercel, I could add a console.log() and view the server logs to debug, how do I go about doing that with Cloudflare?
I've looked at realtime logs, but they only seem to contain headers.
JYou should be able to log errors and view them when tailing your deployment with wrangler
Rcan anyone give me a link to a repository where latest nextjs is working with other features of cf like kv?
MHello
MI have a small problem with cloudflare if anyone can help me...
MI have a website made with next and cloudflare
MBut, the problem is that, when I use the next
<Image /> component it doesn't work, and no images serve even the static in the public directoryMHow to solve this
JIf you do
pnpm create cloudflare it will initialise a new Next.js project for you. In there, you will find commented out example usage of KV. You can uncomment this in next.config.mjs, env.d.ts, and app/api/hello/route.ts. Then if you run your app, you will see it putting + getting with kv
JThere are a variety of commands you can run with wrangler for d1, such as migrations or executing sql. i would recommend using the d1-database channel if you want help with d1.
JYeah I'm afraid the miniflare bindings for next dev are only local and won't be able to connect to a remote database
Byes it is
