Revert "Return empty .json() object on 204. Fix #165. (#166)"

[TimothyGu]

This reverts commit 95b5893.

Fixes #165.

[hmarr]

Hello! Any chance this could be back-ported to a 1.x.x release? Not throwing the error broke compatibility with browser fetch implementations, so I'd consider this commit a fix that gets us back to the previous desired behaviour.

Thanks!

[bitinn]

It's been a while since I looked at 1.x release, if it's indeed affected I can take a PR to fix it. PS: 2.x should be ready for use if you want to. We don't intend to backport spec related changes to 1.x if possible (as 2.x is intended to address this issue without raising too much upgrade problems). (From my phone)

…

在 2017年5月22日，18:33，Harry Marr ***@***.***> 写道： Hello! Any chance this could be back-ported to a 1.x.x release? Not throwing the error broke compatibility with browser fetch implementations, so I'd consider this commit a fix that gets us back to the previous desired behaviour. Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[hmarr]

Ok, thanks @bitinn. What's the ETA for a 2.0 final release?

I'm using node-fetch via fetch-mock, which depends on 1.x, and I imagine they'd want to wait for a non-prerelease of v2 before upgrading.

If it's going to be a while off, I'll put in a PR for 1.x doing the backport.

[bitinn]

@hmarr actually I have already fixed it in recent v1.7.0 release :)

[hmarr]

@bitinn brilliant, thanks!