I see that this PR has been merged, maybe it is already fixed or is it not in prod yet?
I see that this PR has been merged, maybe it is already fixed or is it not in prod yet?
Dno, I'm sure it is not in prod as they haven't released it yet (https://github.com/cloudflare/workerd/releases)
BMy .env file atm has nothing in it related to bindings, well when it worked using process.env I was using this:
Now: (working local but not in production)
Now: (working local but not in production)
DMy .env file atm has nothing in it related to bindingsweird
the
env.d.ts.envso right now you have an application and in it you can do
process.env.DBgetRequestContext().env.DB@Befus PS: I just noticed this issue on github: https://github.com/cloudflare/next-on-pages/issues/675 I'm not sure if that's you, anyways I just thought of pointing it out to you 
, I'll look into that as soon as I can
, I'll look into that as soon as I canGitHub
If I understand correctly, version 1.9.0 removes the possibility to access your process.env.DB dev binding outside of a Route Handler. When using the v5/beta version of next-auth / auth.js, you nee...
BLol thats not me but the exact same issue lol
Bprocess.env.DB doesn't work atm because i am only using env.d.ts which has the cloudflareEnv inside of it alongside with getRequestContext
This works locally perfectly fine but on production/preview it fails
This works locally perfectly fine but on production/preview it fails
Das I said
env.d.ts(process.env as any).DBBuild seems successful when using this:
BGonna test if it actually works
BSeems to be working fine now
Dwhat if you try using
getOptionalRequestContextprocess.env
GIs it expected that static assets return an ETag but routes api url don't? I've migrated my app to next-on-pages from a pre-existing expressjs app and that's a key difference. I wonder if I should manually add the Etag computation on my routes or if that would be discouraged to do so? Is there a setting that would enable so in next-on-pages or cloudflare's config?
Bok so we upgraded and the site is now live. but it is slow like slow. like the page doesnt even open. and we have to refresh multiple times. when i run it locally using the wrangler command, it is crazy fast. not sure what is going on here
Bi get this error a lot.
B
EHey everyone!
I recently added a _headers file to my Next.js application's public directory to set some headers, but it doesn't seem to be working as expected.
I'm curious to know how this affects the entire application. Does it impact all routes, pages, or any other aspects I should be aware of?
Thanks in advance for any insights you can provide!
I recently added a _headers file to my Next.js application's public directory to set some headers, but it doesn't seem to be working as expected.
I'm curious to know how this affects the entire application. Does it impact all routes, pages, or any other aspects I should be aware of?
Thanks in advance for any insights you can provide!
CIf its not statically generated, you'll probably need to use a config rule
BLooks like it got released yesterday
DCan
getRequestContext
BBoth
DI was confused because of this:
https://github.com/cloudflare/next-on-pages/issues/675#issuecomment-1959426101
https://github.com/cloudflare/next-on-pages/issues/675#issuecomment-1959426101
GitHub
If I understand correctly, version 1.9.0 removes the possibility to access your process.env.DB dev binding outside of a Route Handler. When using the v5/beta version of next-auth / auth.js, you nee...
BAre you using drizzle aswell?
BThats the temporary solution for getting the drizzle connection to work, not sure why this is at the moment but I had to do this myself aswell
DNo, I am just making sure if all the bindings are made available for both production and development through
Thank you for the reply
getRequestContextThank you for the reply
BYea I would say test it out as it should work for both but if it doesn't then that's the solution I used in my case
Dyes thanks I saw 
(according to this comment: https://github.com/cloudflare/workerd/issues/1513#issuecomment-1958520069)
the fix will be included in production next week, hopefully it fixes our problems
(I am not really that familiar with the process to be honest, but it sounds like, when there's a workerd release that doesn't automatically get deployed to production right away, so we'll have to wait till it does I guess)
(according to this comment: https://github.com/cloudflare/workerd/issues/1513#issuecomment-1958520069)
the fix will be included in production next week, hopefully it fixes our problems
(I am not really that familiar with the process to be honest, but it sounds like, when there's a workerd release that doesn't automatically get deployed to production right away, so we'll have to wait till it does I guess
)
D
BgetRequestContext
ZHi guys! I'm new to cloudflare and I need some help regarding Static forms from Cloudflare Pages. I have a next project where I need to intercept a form from the cloudflare side. I saw this usage guide [https://developers.cloudflare.com/pages/functions/plugins/static-forms/] in the cloudflare docs where we could use a
Here are my form html and also my _middleware.ts file.
Note: I'm handling the form in a controlled way in react so I'm handling the inputs state and also form submission. (Could this be the issue?)
Can you guys help me or did you already had this issue before?
_middleware.ts functionsHere are my form html and also my _middleware.ts file.
Note: I'm handling the form in a controlled way in react so I'm handling the inputs state and also form submission. (Could this be the issue?)
Can you guys help me or did you already had this issue before?
JIf you're using
@cloudflare/next-on-pages
WIm also here with a broken next-on-pages + Drizzle D1 App. Are there any docs on setupDevPlatform? Not sure how to upgrade my app
LAre there any docs for next-on-pages + durable objects? 
BGitHub
If I understand correctly, version 1.9.0 removes the possibility to access your process.env.DB dev binding outside of a Route Handler. When using the v5/beta version of next-auth / auth.js, you nee...
DHi @wesbos 
These are the docs for the next-dev submodule and show you how to use
Please have a look and let me know if it's all clear
(PS: if you were using
(regarding Drizzle yeah we've gotta wait till next week to see if that's all fixed on the runtime I'm afraid)
(regarding Drizzle it should hopefully be all good now
)
These are the docs for the next-dev submodule and show you how to use
setupDevPlatformPlease have a look and let me know if it's all clear
(PS: if you were using
setupDevBindingswrangler.toml(regarding Drizzle it should hopefully be all good now
)GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
D@wesbos could you tell me if/how you've looked for the
I would love it if it would be easily discoverable and I hoped that this would do the trick:
https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflare-platform-integration
but if you had issues finding it maybe we've got a discoverability issue here? what do you think?
setupDevPlatformI would love it if it would be easily discoverable and I hoped that this would do the trick:
https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflare-platform-integration
but if you had issues finding it maybe we've got a discoverability issue here? what do you think?
GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
Dthis is what we've got 
: https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev#next-on-pages-next-dev
it briefly mentions DOs but that's acutally not too too helpful I'm afraid.... I'll add a note here: https://developers.cloudflare.com/workers/wrangler/api/#getplatformproxy
to better explain how to access DOs using
Anyways to use DOs you need to define them in your wrangler.toml file in this way:
and then before you run your next-on-pages app, in a separate terminal you need to spin up your "do-worker" worker
(you can't define a DO in your next-on-pages app but use the DO from a different worker)
I hope this helps, please let me know if it does
: https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev#next-on-pages-next-devit briefly mentions DOs but that's acutally not too too helpful I'm afraid.... I'll add a note here: https://developers.cloudflare.com/workers/wrangler/api/#getplatformproxy
to better explain how to access DOs using
getPlatformProxyAnyways to use DOs you need to define them in your wrangler.toml file in this way:
and then before you run your next-on-pages app, in a separate terminal you need to spin up your "do-worker" worker
(you can't define a DO in your next-on-pages app but use the DO from a different worker)
I hope this helps, please let me know if it does
WOh thanks! Apologies for not seeing that. My process was to google next-on-pages, which lead me to the github repo, I read that whole thing and then clicked each of the βreferencesβ links, then googled the method, didnβt see anything and then came here. I didnβt realize next-dev was a different module, would be great if there was a link in the main readme.
Dthere is!
D
WJust seeing now ugh
WYou can see the packages contents (with their documentation)
WSorry I just scrolled to the bottom and clicked the docs links. That might by be a user issue and not a docs issue haha
DI see
well it's valuable feedback in any case! thanks a bunch!
well it's valuable feedback in any case! thanks a bunch!
Dprobably having the next-dev module as a separate "internal package" helps making this a bit more confusing.... I would look into bring it into the next-on-pages package and remove this extra separation
WYeah, at least some docs on getting started without npx, I think a lot of people come at it from already having a next site and now want to figure out how to get it ready and bind services locally
D(I have an idea on how to do that, I'll need to experiment a bit with it.... the main problem being that the next-on-pages code outputs esm, but the next-dev code needs to output cjs since it gets required by the next dev server)
WI donβt envy that, I tried to convert a next project to ESM and I cried
Da migration doc right?
