is there a entry point for installing an application-level instance of asynclocalstorage?
is there a entry point for installing an application-level instance of asynclocalstorage?
Sfor next-on-pages
Si could wrap all my /api/ handlers (and server components if that works)
Sbut if there's one place, i'd rather do that
JThere is not. Are you able to share an example use case you're thinking of for being able to do so?
DHi all, if I want to use turso db with a full stack nextjs app deployed on pages, do I need to initialize the db on every next API endpoints? Or can I just create a file and export the db and import to endpoints could it work?
BHi all, Cloudflare page not working NextJS14 Node v18.17.1
HWhat is your deploy command?
HShould be something like
wrangler pages deploy .vercel/output/staticyeah that looks like using the wrong output directory
BI changed the build configurations
DHi, there can I ask how did managed using turso with nextjs?
Mok so got allot of stuff working but i am trying to debug my pages but the errros keep showing up like this
is there any way for it to show the actual data it was passed instead of object ?
is there any way for it to show the actual data it was passed instead of object ?
Mmigh hvae figured it out
DAnyone used turso with nextjs?
DIn the web UI there only D1 biding integration
NHey, I just found out that nextjs default image resizing doesn't work with next on pages, is this intended?
NThe returned image is always at its original size
Jyes, it's not possible for us to do image resizing on the server in pages until the images team adds support to do that
Bsrc/server/utils.ts
is this fine?
is this fine?
getRequestContext()process.envright now process.env works on local, but getRequestContext doesn't, when it always did in the past, very weird
Dboth
(and you should ideally always use
If either doesn't work in some scenario, could you please open an issue (ideally with a minimal reproduction): 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+
so that I can take a look and address the bug?
(most definitely you should not have to define utility functions like the one you shared!
)
getRequestContext()process.envnext devwrangler pages dev(and you should ideally always use
getRequestContext()If either doesn't work in some scenario, could you please open an issue (ideally with a minimal reproduction): 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+
so that I can take a look and address the bug?
(most definitely you should not have to define utility functions like the one you shared!
)Bill make a repro once i can
Bbut the idea is
server component -> server action -> server utility - (getRequestContext() doesn't work here)
server component -> server action -> server utility - (getRequestContext() doesn't work here)
Dmh... odd 
Dthanks, I'll give it a try 
(but yeah a repro would definitely speed things up 
)
(but yeah a repro would definitely speed things up )
BGitHub
Contribute to sunneydev/next-on-pages-env-bug-repro development by creating an account on GitHub.
Bhere
Bseems like its only for environment variables
Bthat are defined in
.envor maybe for other ones as well, not sure exactly
Bah the action doesn't work as well, no need 3rd (utility) layer at all
Bso like its for
.envnextjs accounts for them in process.env but not
getRequestContext()
Doh....
Btldr bindings work, env variables defined in
.envgetRequestContext()you're not using
.dev.varsnope, regular
.env.dev.varsyeah that's not going to work
(I did try to convince the team to fix this but it seems like people are happy with the current way of not reading the
)
(I did try to convince the team to fix this but it seems like people are happy with the current way of not reading the
.envyes, you should have a
.dev.vars.envCloudflare Docs
Store sensitive information, like API keys and auth tokens, in your Worker.
Bthats fine im ok with that, but its crucial that these edge cases should be documented in a single place somwhere as a lot of nextjs devs will run into these kind of issues
Dyes.... that's a totally valid point....
Band i dont think a lot of people will play close attention to github docs as not a lot of people use github for docs, maybe have a separate website for this? idk
DGitHub
It would be very convenient if https://developers.cloudflare.com/pages/framework-guides/deploy-a-nextjs-site/ also mentioned that for Next.js (and its command dev) you can use the .env file as usua...
Dyes I can see your point.... we did add a troubleshooting section to our Next.js guide: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#troubleshooting
Cloudflare Docs
Deploy a full-stack Next.js site (recommended).
DI guess I should add this there too 
Bis
cache supported btw?B
