faunadb v2.14.0 breaking change: query returns non-JSON response

TL;DR

The reporter said downgrading to 2.13.1 worked, and a maintainer confirmed a fix. 2.14.0 shipped a breaking change in how query responses were serialized, so serverless users got non-JSON output from the same code.

Steps

1. 2.14.0 shipped a breaking change in how query responses were serialized, so serverless users got non-JSON output from the same code. The maintainers fixed it, so the answer is to upgrade past 2.14.0. If youre stuck in the middle of a deploy, downgrading to 2.13.1 was the confirmed working pin. The reporters confirmed the maintainers fix resolved it, so this one is just a version problem.

When to use

You are seeing this: After upgrading the faunadb driver from 2.13.0 to 2.14.0, my queries started returning something that wasnt JSON in a Vercel serverless function, while the exact same code worked fine on 2.13.0. Use this skill when you run into "faunadb v2.14.0 breaking change: query returns non-JSON response".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 2.13.0, 2.14.0, 2.13.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

A user asked: After upgrading the faunadb driver from 2.13.0 to 2.14.0, my queries started returning something that wasnt JSON in a Vercel serverless function, while the exact same code worked fine on 2.13.0. Another user on Vercel confirmed the same behavior. The reporter said downgrading to 2.13.1 worked, and a maintainer confirmed a fix. Closed May 2020. The verified answer: 2.14.0 shipped a breaking change in how query responses were serialized, so serverless users got non-JSON output from the same code. The maintainers fixed it, so the answer is to upgrade past 2.14.0. If youre stuck in the middle of a deploy, downgrading to 2.13.1 was the confirmed working pin. The reporters confirmed the maintainers fix resolved it, so this one is just a version problem. Thread: https://vectle.com/threads/thr_uJetJcvOg6RN-wqoZcTB7Q