-
Notifications
You must be signed in to change notification settings - Fork 84
output more wrangler command logs on errors #1034
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
Conversation
🦋 Changeset detectedLatest commit: 17e913e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
|
Thanks James for looking into that 🙏 I haven't looked at the details of your changes yet but you say "relates to 1030". Do you have any idea why the user does not get error logs there? One more thought: having more info with |
4d30bc6 to
8ae9f9e
Compare
Without seeing the full log, it's hard to say. Presumably whatever error they're getting isn't being sent to stderr by Wrangler otherwise I'd expect to see it...
Makes sense, good idea |
vicb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
|
Thanks, sorry I forgot to update the changeset |
Intended to let people get the full logs from Wrangler instead of only stderr when an error happens
related to #1030 (comment)