Uploading failed

While trying to update the old project I run to issue where im trying to basically commit new files. I have issue with probably PageTransition but dont know why when building of project is going well.
No description
No description
24 Replies
Tom4sko
Tom4skoOP2w ago
the issue might be with
No description
No description
James
James2w ago
My immediate guess would be the filename being slightly different. In Windows, file names are case insensitive so pagetransition and PageTransition and pageTransITION are all the same thing In Linux where this builds like in Pages CI, things are case sensitive. So if the file isn't it Git as exactly PageTransition, it's going to have a hard time resolving it. Otherwise, if you can throw up a minimal reproduction onto GitHub or similar, I can take a closer look
Tom4sko
Tom4skoOP2w ago
Hello James, thank you so much. Here is the repo
Tom4sko
Tom4skoOP2w ago
GitHub
GitHub - Tom4sko/GoldWinBox
Contribute to Tom4sko/GoldWinBox development by creating an account on GitHub.
James
James2w ago
yeah I think my theory is correct. In git that file is pageTransition.tsx note the lowercase p So in Linux where it's case sensitive, PageTransition with a capital P doesn't exist
Tom4sko
Tom4skoOP2w ago
K let me try, because before i always used new git commit
No description
Tom4sko
Tom4skoOP2w ago
and it is weird it didnt changed
Tom4sko
Tom4skoOP2w ago
because i always had it with big P
No description
James
James2w ago
windows is going to make that painful to change I'd recommend a git mv -f pageTransition.tsx PageTransition.tsx and then commit via cli
Tom4sko
Tom4skoOP2w ago
This is what i did
git mv -f pageTransition.tsx PageTransition.tsx
git mv -f pageTransition.tsx PageTransition.tsx
, before, I just changed the name of file and commited and didnt check if that changed or not
James
James2w ago
ah yes I see PageTransition.tsx now What's the error you're getting now? It's likely this'll affect a few files you have that are case mismatched
Tom4sko
Tom4skoOP2w ago
16:33:59.111 ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
James
James2w ago
Can you provide the full log?
James
James2w ago
2024-12-28T15:33:59.11146Z ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
2024-12-28T15:33:59.1116Z ⚡️
2024-12-28T15:33:59.111699Z ⚡️ The following routes were not configured to run with the Edge Runtime:
2024-12-28T15:33:59.111786Z ⚡️ - /api/send
2024-12-28T15:33:59.111873Z ⚡️
2024-12-28T15:33:59.112283Z ⚡️ Please make sure that all your non-static routes export the following edge runtime route segment config:
2024-12-28T15:33:59.11253Z ⚡️ export const runtime = 'edge';
2024-12-28T15:33:59.112857Z ⚡️
2024-12-28T15:33:59.113004Z ⚡️ You can read more about the Edge Runtime on the Next.js documentation:
2024-12-28T15:33:59.11312Z ⚡️ https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes
2024-12-28T15:33:59.11146Z ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
2024-12-28T15:33:59.1116Z ⚡️
2024-12-28T15:33:59.111699Z ⚡️ The following routes were not configured to run with the Edge Runtime:
2024-12-28T15:33:59.111786Z ⚡️ - /api/send
2024-12-28T15:33:59.111873Z ⚡️
2024-12-28T15:33:59.112283Z ⚡️ Please make sure that all your non-static routes export the following edge runtime route segment config:
2024-12-28T15:33:59.11253Z ⚡️ export const runtime = 'edge';
2024-12-28T15:33:59.112857Z ⚡️
2024-12-28T15:33:59.113004Z ⚡️ You can read more about the Edge Runtime on the Next.js documentation:
2024-12-28T15:33:59.11312Z ⚡️ https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes
I'm not familiar with Next.js but looks like you have something there I'd also recommend you set NODE_VERSION env to 20 in your pages config for both preview and prod to avoid all those "unsupported engine" errors
Tom4sko
Tom4skoOP2w ago
okay this hepled me a lot Lets gooo ❤️ thank you James
Tom4sko
Tom4skoOP2w ago
No description
Tom4sko
Tom4skoOP2w ago
for anyone with same issue
James
James2w ago
Nice!
Tom4sko
Tom4skoOP2w ago
hi James, sorry for again disturbing. But when I put my web on live servers. The contanct form stopped working. I added API key to variables and secrets
Tom4sko
Tom4skoOP2w ago
No description
James
James2w ago
I would recommend checking/adding logs for your endpoint to debug this. You can view them via wrangler pages deployment tail: https://developers.cloudflare.com/pages/functions/debugging-and-logging/
Cloudflare Docs
Debugging and logging · Cloudflare Pages docs
Access your Functions logs by using the Cloudflare dashboard or the Wrangler CLI.
Tom4sko
Tom4skoOP2w ago
I debugged almost every line and on localhost it is working, but not on server. How that can be possible
James
James2w ago
What do the server logs show if you add logs before/after the API functionality? Something must be different - missing API key, etc. Adding logs and then debugging the production version is going to be your best option

Did you find this page helpful?