Joseph Procopio

Results 5 comments of Joseph Procopio

same issue. when i do it locally no issues. When i deploy, this is happening on cloudflare pages. did you ever resolve?

Another example that should return a 401, but gives a 500. again this works locally and on vercel, but not on cloudflare pages: ```js const GET = async (req: NextRequest)...

This happens on "next": "^14.0.4", i reverted to "next": "13.1.5", and do not have this issue

Hey! thank you for the help here. Ive been wracking my brain with this for awhile and not sure what I'm missing here. I cant get inngest to discover this...

Hmm, I don't think thats the problem. I was actually able to solve that a different way off the AWS server just using Mangum and FastAPI in a docker container...