have you tried installing the types packages? and eslint?
have you tried installing the types packages? and eslint?
SThis is already present in
package.jsonpackage.jsonOne thing I want to mention is that this is added in dev dependency
Dis it in the yarn lock file and
the command is indeed saying that it can't find them (you did
)
node_modulesthe command is indeed saying that it can't find them (you did
yarn installyeah that's correct 
Dis your project public?
Dah wait!.... sorry I just realized now....
Syes, let me share you a link
Dis the issue local? or only in the Pages CI/CD?
Sin cloudflare build time
Dcan you share your deployment ID?
SYes let me check
Dand then the second hash.... ok
Sthis is good right?
SDyes, thank you, I'm having a look right now
SThanks!
Dit looks like your build command is
npx next buildTried but not working, giving same error
SD@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 installIf 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
developmainit 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://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.tswith the following approach:
Bbut im getting
▲ Error: Failed to retrieve the Cloudflare request context.next buildok.
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!
)
betaprocess.env.DBprocess.envideally devs should always use
getRequestContext()process.envgetRequestContext()(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-handlerI 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
publicSuppose my pages is deployed on
example.comfavicon.icoI used service binding in the same app which tries to fetch
example.com/favicon.icoI 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-pages