-
Notifications
You must be signed in to change notification settings - Fork 748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 BUG: wrangler logs success for pages deploy even with Functions failures #3966
Comments
Happening with me as well. The CLI fails to return a warning. |
hey folks, Thank you so much for raising this issue 🫶 . Really appreciate all the details provided 💖 I'm happy to report there's an open PR that addresses this bug. Really excited to be fixing this, as I think it'll be incredibly helpful for our users moving forward 🤗 Feel free to have a look and make your voice heard wrt the proposed solution. Particularly interested in knowing if the logging we put in place there provides you with sufficient information. Feedback is always much appreciated <3 |
OMG IT Worked now!!! hahahah, My script is over the 1 MiB size limit!! |
Which Cloudflare product(s) does this pertain to?
Wrangler core
What 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
:functions/_middleware.js
:Result via wrangler (
npx [email protected] pages deploy .
):But the Cloudflare Pages dashboard shows an error:
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.
The text was updated successfully, but these errors were encountered: