Skip to content
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

POST and PUT do not log response to console #33

Closed
tim-phillips opened this issue Sep 9, 2017 · 0 comments · Fixed by #35
Closed

POST and PUT do not log response to console #33

tim-phillips opened this issue Sep 9, 2017 · 0 comments · Fixed by #35

Comments

@tim-phillips
Copy link

tim-phillips commented Sep 9, 2017

After upgrading from 1.1.2 to 1.2.2, POST and PUT responses are no longer getting logged to the console. I am seeing responses received by the client.

> #7 PUT /user/name                                                  2:18:34 PM


——————————————————————————————————————————————————————————————————————————————
> #2 POST /                                                          2:22:14 PM


———————————————————————————————————————————————————————————————————————————————

Is anyone else experiencing this?

tungv added a commit to tungv/micro-dev that referenced this issue Sep 10, 2017
`json()` calls will never be resolved in `res.end`

close vercel#33
tungv added a commit to tungv/micro-dev that referenced this issue Sep 10, 2017
`json()` calls will never be resolved in `res.end`

close vercel#33
timneutkens pushed a commit that referenced this issue Sep 12, 2017
…)` (#35)

`json()` calls will never be resolved in `res.end`

close #33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant