Tried but not working, giving same error
Tried but not working, giving same error
S
D@Satyam Bajpai thanks for the ping, sorry I got distracted in other things yesterday 
, I'm having a look right now
, I'm having a look right nowDI've forked your github repository (it should be this one right? https://github.com/satyam73/skill-tree-frontend)
and tried deploying the application, after a few minor adjustments it seems to work as expected:
https://c3f337ae.skill-tree-frontend-7zq.pages.dev/
(if it helps this is my fork: https://github.com/dario-piotrowicz/skill-tree-frontend)
Could you locally run
If it doesn't work please try to apply these changes to your repository: https://github.com/satyam73/skill-tree-frontend/compare/develop...dario-piotrowicz:skill-tree-frontend:develop
and tried deploying the application, after a few minor adjustments it seems to work as expected:
https://c3f337ae.skill-tree-frontend-7zq.pages.dev/
(if it helps this is my fork: https://github.com/dario-piotrowicz/skill-tree-frontend)
Could you locally run
yarn install to update the lock file, push the change and try again?If it doesn't work please try to apply these changes to your repository: https://github.com/satyam73/skill-tree-frontend/compare/develop...dario-piotrowicz:skill-tree-frontend:develop
Doh... I was on the
develop branch, let me try main....Dit seems like what I said above still applies on
(https://main.skill-tree-frontend-7zq.pages.dev/)
(changes I made: https://github.com/satyam73/skill-tree-frontend/compare/main...dario-piotrowicz:skill-tree-frontend:main)
main: https://github.com/dario-piotrowicz/skill-tree-frontend/tree/main(https://main.skill-tree-frontend-7zq.pages.dev/)
(changes I made: https://github.com/satyam73/skill-tree-frontend/compare/main...dario-piotrowicz:skill-tree-frontend:main)
Bwhat is the recommended way of initializing a database with drizzle for example in app router?
I'm trying to initialize it in
with the following approach:
I'm trying to initialize it in
src/server/db.ts with the following approach:
Bbut im getting
▲ Error: Failed to retrieve the Cloudflare request context. error when doing a next build. it works fine in developmentBok.
process.env.NODE_ENV === "development"
? getRequestContext().env.DB
: (process.env as any).DB works
DI am using service bindings in my application, fetching assets in workers leads to 522 response code. Is there any way to fetch static assets from workers on same origins?
D@bun If you use the latest
ideally devs should always use
(PS: if you do have a reproduction that you can share please throw it my way!
)
beta release you can just use process.env.DB both in development and production (process.env not working in development was a bug I've fixed here: https://github.com/cloudflare/next-on-pages/pull/690)ideally devs should always use
getRequestContext() and not process.env, but it seems like getRequestContext() has some bug that makes it not work in some cases, I'll definitely look into that the only thing is that I haven't gotten a minimal reproduction to play with that till now (I did briefly tried to reproduce it with no luck, I should also try that again if I can't get a minimal repro)(PS: if you do have a reproduction that you can share please throw it my way!
)
Dcan you share your code? how are you trying to fetch your assets? have you tried with
kv-asset-handler? (https://github.com/cloudflare/workers-sdk/tree/main/packages/kv-asset-handler)DI want to fetch the static assets in
Suppose my pages is deployed on
I used service binding in the same app which tries to fetch
I need to fetch images files uploaded on pages after build for optimisation using wasm
public folder.Suppose my pages is deployed on
example.comfavicon.ico.I used service binding in the same app which tries to fetch
example.com/favicon.ico.I need to fetch images files uploaded on pages after build for optimisation using wasm
DThe worker fetches files if routed to different origin but respond with 522 when same origin.
Dhttps://fineshop.app/api/image?url=https://fineshop.app/logos/logo-512x512.png&w=256&q=75
https://image.fineshopdesign.workers.dev/image?url=https://fineshop.app/logos/logo-512x512.png&w=256&q=75
First one using service bindings but same workers.
https://image.fineshopdesign.workers.dev/image?url=https://fineshop.app/logos/logo-512x512.png&w=256&q=75
First one using service bindings but same workers.
Bdo you still need a reproduction ?
Dyes 
IWhat version of Wrangler are you using?
JNot sure what you're referring to. The Next.js docs are pretty clear about how API routes are written. Your screenshot above looks like a Pages function, not a Next.js API route, and next-on-pages only supports Next.js, not the functions directory.
J@cloudflare/next-on-pages is for deploying full-stack Next.js apps to Cloudflare Pages. Therefore, you should be using native Next.js features. The functions directory will not work with next-on-pages because we have our own worker to handle your requests. If you want to use the functions directory, you won't be able to use next-on-pagesJIf you want to deploy a full-stack Next.js application, you should use Next.js' features
TIs there any way to force exclude files from the final bundle of a route? I'm trying to use
vercel.json, but it doesn't seem to be working :/SThanks for putting this much efforts @Dario 
Really appreciate your efforts
Could you please tell me what configuration you choose while deploying?
Also, for me, when I am running yarn install in local the changes aren't coming in yarn.lock file and in yours there are changes, so did you have done some other steps too?
Really appreciate your efforts
Could you please tell me what configuration you choose while deploying?
Also, for me, when I am running yarn install in local the changes aren't coming in yarn.lock file and in yours there are changes, so did you have done some other steps too?
Dall the changes I made are there in the commits I shared, besides those and
yarn install, I didn't do anything elseDthis is my configuration
D
Dand I am using the v2 build image
D
D(but I think you were using that too)
D(PS: I also think I've also got a fix for it , but that might not work for your particular case 
)
, BWhat was the cause?
BI believe that error occurs in some specific context of the Next.js app
Dyes, I think it only happens when the
getRequestContext is part of the top-level scope of a file, as you can see here: https://github.com/dario-piotrowicz/next-on-Pages-top-level-getRequestContext-bug-reproGitHub
Contribute to dario-piotrowicz/next-on-Pages-top-level-getRequestContext-bug-repro development by creating an account on GitHub.
Dbasically I think that the Next.js build process, imports the files and that triggers such the
getRequestContext calls to happen, but since you're in nodejs the context is not presentDthe annoying bit is also that prerendering does not work with files using the edge runtime so those calls not working is not something that should really cause issues, but naturally Next.js does need to import those files in order to see if they are exporting the 
edge runtime config DI could very very easily fix it by making
getRequestContext just return undefined during prerendering, but if there is other code that on the top level uses such bindings it could be problematic, so I'll have to experiment and think about it a bit...DMh.... it is quite problematic... I'm thinking that likely the only viable solution is to forbid the use of (and implement a nice error message that makes that clear)
getRequestContext from the top level (and implement a nice error message that makes that clear)DPS: trying to use it alongside bindings top-level does seem to also cause hydration problems, so maybe forbidding it altogether is indeed the right choice 
