Wrangler pages publish always fails (Tried both with NextJS and with Astro templates)

luccas.mateus · September 9, 2023, 2:17pm

Steps to reproduce:

Clone: https://github.com/luccasmmg/astro-template (This is literally just the astro template with the cloudflare integration installed on top)
Run: “npm run build”
Run: “npx wrangler pages deploy dist”

The output says that everything is fine

🌍  Uploading... (2/2)

✨ Success! Uploaded 0 files (2 already uploaded) (0.48 sec)

✨ Compiled Worker successfully
✨ Uploading Worker bundle
✨ Uploading _routes.json
✨ Deployment complete! Take a peek over at `https://5db9391a.portal-datopian-support.pages.dev`

But when i try accessing the cloudflare dashboard i get this

I believe this is a problem with the wrangler cli because i made another minimal reproduction based on the nextjs tutorial in https://developers.cloudflare.com/pages/framework-guides/deploy-a-nextjs-site/ https://github.com/datopian/next-template and the same issue happens.

Note:
Running npx wrangler pages dev dist will work fine

cherryjimbo · September 17, 2023, 12:47pm

Wrangler doesn’t wait for functions deployment it seems, so it reports a success but then something with your Function is error. This creates a pretty poor development experience, sorry about that, but hopefully we can help you get to the bottom of the issue.

Can you share a deployment ID so someone on the Pages team can take a closer look please?

The Pages deployment ID is a unique build identifier.
It’s the UUID in the browser bar (for example, a URL would be dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID where the deployment ID looks something like a398d794-7322-4c97-96d9-40b5140a8d9b).

cherryjimbo · September 17, 2023, 1:06pm

I’ve also created an issue for tracking this kind of thing:

github.com/cloudflare/workers-sdk

🐛 BUG: wrangler logs success for pages deploy even with Functions failures

opened 01:01PM - 17 Sep 23 UTC

Cherry

bug

### Which Cloudflare product(s) does this pertain to? Wrangler core ### Wh…at version(s) of the tool(s) are you using? 3.8.0 ### What version of Node are you using? 18.17.1 ### What operating system are you using? Windows 10 ### Describe the Bug When publishing a Pages project with Functions, wrangler will seemingly always report a success, even if the Functions upload fails. Example: `index.html`: ``` <html> <body> <h1>Hello World</h1> </body> </html> ``` `functions/_middleware.js`: ```javascript const a = true; a(); export function onRequest(context){ return context.next() } ``` Result via wrangler (`npx [email protected] pages deploy .`): ``` ✨ Successfully created the 'test-functions-errors' project. ✨ Compiled Worker successfully 🌏 Uploading... (1/1) ✨ Success! Uploaded 1 files (1.56 sec) ✨ Uploading Functions bundle ✨ Deployment complete! Take a peek over at https://3f676375.test-functions-errors.pages.dev ``` But the Cloudflare Pages dashboard shows an error: ![](https://up.jross.me/mv9n9ifp) And the project isn't actually available. There's no way to get logs about what happened here, so folks are left confused. This happens periodically in Discord, requiring a Pages team member to pull logs for a deployment ID, as well as on the forum such as at https://community.cloudflare.com/t/wrangler-pages-publish-always-fails-tried-both-with-nextjs-and-with-astro-templates/554749?u=cherryjimbo.

Hopefully that’ll be improved so the DX here isn’t as rough.

luccas.mateus · September 19, 2023, 1:44pm

I actually think i’ve just found the issue

I went back in the nextjs tutorial to get a new deployment so that i could provide you with a deployment id, and i saw something that i missed which was the possibility of running npm create cloudflare@latest my-next-app -- --framework=next which automatically does the deployment and low and behold it worked.

But that left me wondering, why does it work here and not when i try to run npx wrangler pages deploy .vercel/output/static --project-name={my project} --branch=main so i started looking into everything in the dashboard and the only thing that i could find different were the compat flags, my project had both nodejs_compat and url_standard while the one created by the npm create cloudflare... cli only had nodejs_compat so i decided removing it and it worked.

I cant exactly remember why i ended up adding it, probably something to do with the fact that i created the project using the API here https://developers.cloudflare.com/api/operations/pages-project-create-project i must’ve read Example: url_standard as Default: url_standard and ended up putting there.

Tested the astro-template without that flag and it worked as well

ANYWAY, i think my problem is pretty much fixed, thanks a lot and sorry for the trouble

system · September 22, 2023, 1:44pm

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.